fix: Add delay between statistics tasks to prevent API flooding#320
Open
fix: Add delay between statistics tasks to prevent API flooding#320
Conversation
When multiple contracts exist, statistics tasks are spawned concurrently which can cause API rate limiting. Added 1 second delay between starting each statistics task.
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
Add a small delay between spawning statistics tasks to prevent API rate limiting.
Problem
When multiple contracts exist, the coordinator spawns statistics tasks concurrently using
async_create_task(). This can cause API rate limiting or flooding when there are many contracts.Solution
Added a 1-second delay between starting each statistics task to space out API requests and prevent rate limiting.