This repository was archived by the owner on Mar 8, 2023. It is now read-only.
Parallel fetch opto #17
Open
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
massive reduction in scrape time
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
This PR changes the scrapes issued to Cloudwatch to all execute in parallel instead of series. It reduces the scrape time needed hugely in my case, going from just under 60 seconds to scrape 80 metrics to less than a second. This in turn means I can poll more frequently and get higher frequency stats imported from Cloudwatch.
The changes are quite small, I would suggest ignoring whitespace changes whilst viewing the diff.
Thx