state-dumper: Don't store state parts in the database #12486
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.