Check state dump time for mainnet #3519
Assignees
Comments
roman-khimov
added
task
AliceInHunterland
added a commit
that referenced
this issue
Jul 24, 2024
Traverse MPT for the current state and dump key/value pairs into file. Close #3519 Signed-off-by: Ekaterina Pavlova <[email protected]>
AliceInHunterland
added a commit
that referenced
this issue
Jul 24, 2024
Traverse MPT for the current state and dump key/value pairs into file. Close #3519 Signed-off-by: Ekaterina Pavlova <[email protected]>
AliceInHunterland
added a commit
that referenced
this issue
Jul 24, 2024
Traverse MPT for the current state and dump key/value pairs into file. Close #3519 Signed-off-by: Ekaterina Pavlova <[email protected]>
AliceInHunterland
added a commit
that referenced
this issue
Jul 29, 2024
Traverse MPT for the current state and dump key/value pairs into file. Example usage: `./bin/neo-go db traverse --config-file config/protocol .mainnet.yml`. Close #3519 Signed-off-by: Ekaterina Pavlova <[email protected]>
|
It was checked for mainnet at 5777148. It took from 6 to 8 minutes on a laptop. The resulting file is 250 Mb. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is your feature request related to a problem? Please describe.
I'm always frustrated when we don't know how long it takes to make a state dump for a real network. Maybe it's seconds, maybe minutes, maybe hours.
Describe the solution you'd like
Traverse MPT for the current state in a special utility (see state sync code that does the same thing effectively) and dump key/value pairs into some file. We need to get an approximate real-life value, so this can be performed on a laptop.
Describe alternatives you've considered
Not a lot. We need to know if it's feasible to create state snapshots on a regular basis.
Additional context
#3493, nspcc-dev/neofs-node#2878.
The text was updated successfully, but these errors were encountered: