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: Forwarding #4265

Open
bw-solana opened this issue Jan 3, 2025 · 0 comments · May be fixed by #3222
Open

Performance: Forwarding #4265

bw-solana opened this issue Jan 3, 2025 · 0 comments · May be fixed by #3222
Assignees

Comments

@bw-solana
Copy link

bw-solana commented Jan 3, 2025

Forwarding is entirely broken by design.

The bandwidth available to swqos peers to send me to forward, by design, is much higher than the bandwidth I have in swqos to the leader, which means that when we're forwarding, the forwarding buffer gets huge since ingest rate >> output rate. But this seems fixable if staked overrides don’t grant more than their own stake amount to peers.

Forwarding is entangled with the scheduler, which is currently in the performance critical path. Forwarding is being split out into separate stage (decouple from banking stage).

@bw-solana bw-solana moved this to In progress in Agave Performance Jan 3, 2025
@bw-solana bw-solana linked a pull request Jan 3, 2025 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: In progress
Development

Successfully merging a pull request may close this issue.

2 participants