-
Notifications
You must be signed in to change notification settings - Fork 132
perf(l1)!: separate Account and storage Column families #5055
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
Conversation
Lines of code reportTotal lines added: Detailed view |
| // TODO(#5195): committing each storage trie individually is inefficient. | ||
| // We would benefit form a mass storage node insertion method. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can't we do it like before, with Trie::collect_changes_since_last_hash()? We can store the changes inside a shared buffer, and dump it in the DB at the end.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I agree, we already have commit_without_storing for that.
That said, the genesis runs exactly once and I think it's quick enough as it is.
The goal is to separate both the trie nodes and flat key value representation for accounts and storage, as they can be updated separately.