Repository navigation
Fork release: watcher stays under the free CPU limit - #8
Merged
Merged
Conversation
The REST release list is 1.6 MB with every asset and took ~8 ms of CPU to parse per run, close to the free plan's 10 ms for a cron run. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
github-actions
Bot
added
vouch:trusted
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
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.
Cloudflare analytics showed the watcher using about 8 ms of CPU per run (P99 9.6 ms), against the free plan's 10 ms per cron run. The REST release list it parsed is 1.6 MB, because it carries every asset of 30 upstream releases.
Already deployed.
🤖 Generated with Claude Code