You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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 <ekt@morphbits.io>
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: