feat(cctp): parallelize attestation fetching with bounded worker pool#1011
Draft
asoliman92 wants to merge 1 commit intomainfrom
Draft
feat(cctp): parallelize attestation fetching with bounded worker pool#1011asoliman92 wants to merge 1 commit intomainfrom
asoliman92 wants to merge 1 commit intomainfrom
Conversation
Circle's attestation API does not support batching, so each task requires a separate HTTP call. Process tasks concurrently using an errgroup capped at 10 workers to avoid sequential bottlenecks on large batches without unbounded goroutine spawning. The 10 cap is simialr to what we have in v1.6 at the moment.
|
Code coverage report:
|
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.
Circle's attestation API does not support batching, so each task requires a separate HTTP call. Process tasks concurrently using an errgroup capped at 10 workers to avoid sequential bottlenecks on large batches without unbounded goroutine spawning. The 10 cap is simialr to what we have in v1.6 at the moment.