Run repo maintenance every 30 mins instead of every 2 hrs to increase throughput #1323
Conversation
This file contains 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
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 change was intended to be committed as part of the "speed up tweaks" mentioned in #1322; analysis of the logs from the manual runs showed running batches of 200 operations every 30 minutes was approximately the sweet spot to maximize processing throughput while ensuring sufficient margin is maintained to safely avoid hitting any GitHub rate limits. GitHub rate limits reset hourly, therefore running the job every 2 hours limits the maximum processing throughput of the workflow by at least 50%.