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
While investigating issue #8447 I've found that the nodes running with RocksDB present a significant worse performance on getEarliestAvailableBlockSlot()
Logs for comparison purpose:
Holesky nodes:
LevelDB node: ./teku --config-file=/etc/teku/teku.yml debug-tools db get-earliest-available-block-slot
Time to retrieve earliest available block slot in the database 183ms
1578560
RocksDB node:./teku --config-file=/etc/teku/teku.yml debug-tools db get-earliest-available-block-slot
Time to retrieve earliest available block slot in the database 25398ms
1591424
The text was updated successfully, but these errors were encountered:
While investigating issue #8447 I've found that the nodes running with RocksDB present a significant worse performance on
getEarliestAvailableBlockSlot()
Logs for comparison purpose:
Holesky nodes:
LevelDB node: ./teku --config-file=/etc/teku/teku.yml debug-tools db get-earliest-available-block-slot
Time to retrieve earliest available block slot in the database 183ms
1578560
RocksDB node:./teku --config-file=/etc/teku/teku.yml debug-tools db get-earliest-available-block-slot
Time to retrieve earliest available block slot in the database 25398ms
1591424
The text was updated successfully, but these errors were encountered: