Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Performance: Window Service #4269

Open
bw-solana opened this issue Jan 3, 2025 · 0 comments
Open

Performance: Window Service #4269

bw-solana opened this issue Jan 3, 2025 · 0 comments

Comments

@bw-solana
Copy link

It takes ~25us per shred to go through the insertion routine and ~90us per shred to go through everything (recovery, flushing metas, etc.).
Image

But as we pump more shreds through the system, these numbers start getting worse. For example, when looking at instances where we pump >45k shreds through, the per shred insertion cost approaches 100us and overall loops cost 300us.
Image

At 100us per shred, we’re only getting 4k shreds through per slot, which means 2k data shreds, which means maybe 8k small transactions per block.

This whole system needs to be made much more efficient.

We also should not be relying so heavily on blockstore as a communication mechanism with repair and replay. We also need to limit how long we can spend in a loop before signaling (we currently flush all writes at the end but can spend 1 second or more in this loop in extreme cases).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Backlog
Development

No branches or pull requests

1 participant