Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Run repo maintenance every 30 mins instead of every 2 hrs to increase throughput #1323

Merged
merged 1 commit into from
Apr 3, 2024

Conversation

javulticat
Copy link
Member

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%.

@javulticat javulticat added the repo-maintenance Will help maintain the repo label Apr 3, 2024
@javulticat javulticat self-assigned this Apr 3, 2024
@javulticat javulticat merged commit 2efe244 into master Apr 3, 2024
6 checks passed
@javulticat javulticat deleted the jav/cleanup-inactive branch April 3, 2024 20:17
@coveralls
Copy link

Coverage Status

coverage: 74.831%. remained the same
when pulling 6af7bb9 on jav/cleanup-inactive
into c74a861 on master.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
repo-maintenance Will help maintain the repo
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants