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
After finishing the Lazy Loading would be nice to track how things have improved according to next params:
Reduce memory usage
We want to reduce the memory usage of our nodes, we are aware that a big part of that memory is used to store the in-memory trie, so the first improvement will be reducing the memory used by the state trie lazy loading only the most frequently used tries.
Node startup time
Currently when we are starting up a node using an snapshot, for example 90 gb size, it takes more than 1hr to initialize.
That's because we are loading the storage into our in-memory trie, this should be fixed when we start using lazy loading
The text was updated successfully, but these errors were encountered:
P1sar
added
P-low
this is mostly nice to have.
and removed
Epic
Issue used to track development status of a complex feature, aggregates several issues
labels
May 6, 2024
P1sar
changed the title
Reduce memory usage
Benchmark node parametrs
May 6, 2024
timwu20
changed the title
Benchmark node parametrs
Benchmark node parameters
Jun 19, 2024
Description
After finishing the Lazy Loading would be nice to track how things have improved according to next params:
Reduce memory usage
We want to reduce the memory usage of our nodes, we are aware that a big part of that memory is used to store the in-memory trie, so the first improvement will be reducing the memory used by the state trie lazy loading only the most frequently used tries.
Node startup time
Currently when we are starting up a node using an snapshot, for example 90 gb size, it takes more than 1hr to initialize.
That's because we are loading the storage into our in-memory trie, this should be fixed when we start using lazy loading
The text was updated successfully, but these errors were encountered: