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

state-dumper: Don't store state parts in the database #12486

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

marcelo-gonzalez
Copy link
Contributor

@marcelo-gonzalez marcelo-gonzalez commented Nov 19, 2024

When the state dumper genrates state parts to upload to GCS, it stores them in the StateParts column before doing so. But it never reads these parts after storing them. Storing these parts is not a free operation, because on a forknet run with recent mainnet state, just the storage of the part took on the order of 50-100 millis. Over several thousand parts, that's a nontrivial slowdown for no good reason.

When the state dumper genrates state parts to upload to GCS, it stores
them in the StateParts column before doing so. But it never reads these parts after storing them.
Storing these parts is not a free operation, because on forknet run with recent mainnet state, just
the storage of the part took on the order of 50-100 millis. Over several thousand parts, that's a nontrivial
slowdown for no good reason.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant