feat: add configurable RPC concurrency (cherry-pick #714)#816
Open
fakedev9999 wants to merge 1 commit into
Open
feat: add configurable RPC concurrency (cherry-pick #714)#816fakedev9999 wants to merge 1 commit into
fakedev9999 wants to merge 1 commit into
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
RPC_CONCURRENCYenv var.buffered(10)and.buffered(15)with configurable values (default: 10)Context
The EigenDA FP proposer hits 429 rate limits on both Alchemy and QuikNode during witness generation prefetch. The hardcoded concurrency values create unbounded RPC bursts that exceed provider limits. Setting
RPC_CONCURRENCY=5keeps requests under the 50/sec threshold.Test plan
RPC_CONCURRENCY: "5"and QuikNode L1_RPC