Open oleksandrSydorenkoJ opened 2 months ago
> eth.syncing
{
currentBlock: 1497073,
healedBytecodeBytes: 0,
healedBytecodes: 0,
healedTrienodeBytes: 0,
healedTrienodes: 0,
healingBytecode: 0,
healingTrienodes: 0,
highestBlock: 1523128,
startingBlock: 1497001,
syncedAccountBytes: 0,
syncedAccounts: 0,
syncedBytecodeBytes: 0,
syncedBytecodes: 0,
syncedStorage: 0,
syncedStorageBytes: 0,
txIndexFinishedBlocks: 0,
txIndexRemainingBlocks: 0
}
Could be fixed by https://github.com/skalenetwork/skaled/issues/1545
Describe the bug The indexer node continuously catches up with new blocks, and on slower instances, this prolonged process slows Skaled's JSON-RPC server.
Preconditions Whitelisted IP for Instance with 4GB RSS, 2 cores The long-turn load tests of token transfer with 100k gas usage
Versions: skalenetwork/schain:3.19.1
To Reproduce
Expected behavior The "eth_getBlockByNumber" call should be processed in less than 1 second
Actual state After exhausting all RSS on the instance (4GB), Skaled's JSON-RPC server is slow down and throws the "Performance warning" logs. Indexer node is behind core node by 30k blocks