feat: add weekly per-source item-retention prune cron#10
Merged
Conversation
Adds a second Cron Trigger (Sunday 23:00 ICT) that deletes all but the most recent FEEDREADER_MAX_ITEMS_PER_SOURCE (default 1000) items per source, keeping the items table and every full-table-scan query against it bounded as more sources get added. 1000/source was sized against D1's rows-read quota, not disk: live prod data showed ~700-750 bytes/row and per-source velocity slow enough that even 4 sources at the cap stay well under D1 Free's 500MB limit, but listFeedItems reads sources*cap rows per unfiltered request with no SQL LIMIT, which is the actual scaling risk against the 5M-rows/day free budget. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
|
🔎 Cloudflare preview: https://62bb8302-feedreader.phatpham9.workers.dev Uploaded from |
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.
Adds a second Cron Trigger (Sunday 23:00 ICT) that deletes all but the most recent FEEDREADER_MAX_ITEMS_PER_SOURCE (default 1000) items per source, keeping the items table and every full-table-scan query against it bounded as more sources get added.
1000/source was sized against D1's rows-read quota, not disk: live prod data showed ~700-750 bytes/row and per-source velocity slow enough that even 4 sources at the cap stay well under D1 Free's 500MB limit, but listFeedItems reads sources*cap rows per unfiltered request with no SQL LIMIT, which is the actual scaling risk against the 5M-rows/day free budget.