chore: improve prune #2465
Merged
chore: improve prune #2465
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
MatusKysel
approved these changes
May 3, 2023
mfrankovi
force-pushed
the
prune_replace_column
branch
2 times, most recently
from
e44e39e to
919f67a
Compare
mfrankovi
force-pushed
the
prune_replace_column
branch
from
919f67a to
db9c16c
Compare
kstdl
approved these changes
May 4, 2023
|
prnet cleaned-up successfully |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Review this as well:
Taraxa-project/taraxa-evm#165
Main and account node databases are huge with large number of entries. Any prune where deleting these entries one by one is taking a very long time. This is avoided by having prune load the data in memory that is to be kept and than deleting the entire column in the database at once and recreating it and populating it with data stored in memory. This makes the prune run in about 3 minutes for a month of data.
Since the prune is relatively fast it can be started manually but it is also run on restart for a light node.