Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Optimize Database Size with Shorter Hashes #2744

Open
adamkrellenstein opened this issue Nov 20, 2024 · 0 comments
Open

Optimize Database Size with Shorter Hashes #2744

adamkrellenstein opened this issue Nov 20, 2024 · 0 comments

Comments

@adamkrellenstein
Copy link
Member

adamkrellenstein commented Nov 20, 2024

Combine/refactor/drop/truncate ledger_hash, messages_hash, txlist_hash and event_hash (which should be event_id). We don't need nearly so much entropy there—we need collision resistance only.

We can do more things like avoid storing the tx_hash in tables of transactions. It's a foreign key, so it doesn't use much extra space on its own, but it bloats the messages table. Obv. we have to be careful not to sacrifice performance with this step. EDIT: tx_hash isn't even a foreign key here! I think it should be, along with tx_index, block_index, etc.

@adamkrellenstein adamkrellenstein changed the title Optimize Database Size by Refactoring Hashes Optimize Database Size with Shorter Hashes Nov 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant