-
Notifications
You must be signed in to change notification settings - Fork 782
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
Make beacon processor queue sizes dynamic #5573
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good, very simple. I was thinking of dynamic as adjusting the queue size as the validator set grows but doing it once at startup is a big gain for very little complexity 👍 I don't think it's clear that fully dynamic is really worth the complexity.
I made a minor suggestion, feel free to take it or leave it.
0b8f4eb
to
35ac9f4
Compare
Nominating this for 5.2 as we are increasingly seeing queues filling up shortly after a restart |
Squashed commit of the following: commit 35ac9f4 Author: dapplion <[email protected]> Date: Thu May 30 13:15:50 2024 +0300 Review PR commit 7a4e44b Author: dapplion <[email protected]> Date: Fri Apr 12 16:24:44 2024 +0900 lint commit 7590494 Author: dapplion <[email protected]> Date: Fri Apr 12 16:05:06 2024 +0900 Update tests commit 9460d58 Author: dapplion <[email protected]> Date: Fri Apr 12 15:17:27 2024 +0900 Make beacon processor queue sizes dynamic
Squashed commit of the following: commit 35ac9f4 Author: dapplion <[email protected]> Date: Thu May 30 13:15:50 2024 +0300 Review PR commit 7a4e44b Author: dapplion <[email protected]> Date: Fri Apr 12 16:24:44 2024 +0900 lint commit 7590494 Author: dapplion <[email protected]> Date: Fri Apr 12 16:05:06 2024 +0900 Update tests commit 9460d58 Author: dapplion <[email protected]> Date: Fri Apr 12 15:17:27 2024 +0900 Make beacon processor queue sizes dynamic
Squashed commit of the following: commit 35ac9f4 Author: dapplion <[email protected]> Date: Thu May 30 13:15:50 2024 +0300 Review PR commit 7a4e44b Author: dapplion <[email protected]> Date: Fri Apr 12 16:24:44 2024 +0900 lint commit 7590494 Author: dapplion <[email protected]> Date: Fri Apr 12 16:05:06 2024 +0900 Update tests commit 9460d58 Author: dapplion <[email protected]> Date: Fri Apr 12 15:17:27 2024 +0900 Make beacon processor queue sizes dynamic
@Mergifyio queue |
✅ The pull request has been merged automaticallyThe pull request has been merged automatically at 2c971fa |
Issue Addressed
Some users have complained of their nodes rejecting attestations due to full queues. The current size of 16k was good before, but it's insufficient for the current mainnet's size. Instead of playing catch with these numbers, we can make them dynamic on the validator set size. The set size is not meant to change significantly between client restarts so sampling once at start-up should be sufficient.
Proposed Changes
Make beacon processor queue sizes dynamic, and some of its values variable on initial active validator set size. This change allows future testing of the processor where we want to make the queue very short to test their behavior.
NOTE: I have not changed any numbers except for
attestation_queue
,unknown_block_attestation_queue
. Happy to change or justify existing numbers if you have rationales.