-
-
Notifications
You must be signed in to change notification settings - Fork 317
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
fix: use correct by peer rate limiting on BlobSidecarsByRoot/Range post-electra #7405
base: unstable
Are you sure you want to change the base?
Conversation
…bSidecarsByRoot/Range
also it seems like we might not be applying correct rate limit for
|
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## unstable #7405 +/- ##
============================================
- Coverage 48.45% 48.44% -0.02%
============================================
Files 602 602
Lines 40387 40396 +9
Branches 2069 2069
============================================
Hits 19568 19568
- Misses 20781 20790 +9
Partials 38 38 |
Performance Report✔️ no performance regression detected Full benchmark results
|
Reworked the branch a bit, also handles updating limit if we register protocol for new hard fork. I confirmed that correct electra rate limits are applied on devnet-5, however it's hard to check if fork transition works correctly there since we are already on electra fork and limits are applied based on clock slot but added a unit test to confirm rate limiter is updated as expected. |
I am still seeing occasional rate limits on peers, seems to be always Teku
Edit: these are expected somewhat since I had low peer count and was syncing from far back, rate limiting does not seem to be an issue using this branch as it is less likely to happen |
191adbc
to
ed9aa8b
Compare
Motivation
The by peer rate limiting needs to be increased post-electra from 768 to 1152 as otherwise we might incorrectly rate limit our peers.
Description
Use correct fork constants to apply by peer rate limiting on BlobSidecarsByRoot/Range
rateLimitQuotas
fork-aware, it will apply the new rate limiting during protocol registration of the next fork