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.

Sign up for GitHub

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

Jump to bottom

Determine if storing StateDB, Storage, Transactions, Receipts in one Trie hurts performance #622

Open
willmeister opened this issue Nov 15, 2018 · 0 comments
Open

Determine if storing StateDB, Storage, Transactions, Receipts in one Trie hurts performance #622

willmeister opened this issue Nov 15, 2018 · 0 comments

Comments

@willmeister
Copy link
Contributor

There is a branch (mf-wm-optimize-mpt) that has some code changes that split the State DB off from the rest of the Tries to see if that improves performance, but disk read latency seems to be the main bottleneck, so this can only be fixed after #621
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@willmeister