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
solWinInsert spends ~10% of the time deserializing bincode columns from rocks.
What's in there? why is it bincode? If it must be bincode, we should write hand crafted parsers like the one Alessandro wrote for VoteState which is ~3000x faster than the bincode crate.
~5% of shred recv is actually writing shreds inside rocksdb, half of which is pagefaulting the memtable (we probably have configured the memtable to be too small, so it's getting grown). The other half is performing write syscalls to the filesystem. We probably need to configure much larger buffers.
Some initial (raw) commentary on Blockstore perf
solWinInsert spends ~10% of the time deserializing bincode columns from rocks.
What's in there? why is it bincode? If it must be bincode, we should write hand crafted parsers like the one Alessandro wrote for VoteState which is ~3000x faster than the bincode crate.
~5% of shred recv is actually writing shreds inside rocksdb, half of which is pagefaulting the memtable (we probably have configured the memtable to be too small, so it's getting grown). The other half is performing write syscalls to the filesystem. We probably need to configure much larger buffers.
Completed Items
Inflight Items
Potential Future Work
The text was updated successfully, but these errors were encountered: