Repository navigation
Record the 2026-10-28 catalog refresh and the REV cron's production CPU - #56
Merged
Merged
Conversation
[Low impact] This documentation-only PR appears safe to merge. SummaryRecords the 2026-10-28 catalog refresh and REV's production CPU measurements.
No actionable issues were found. Reviews (1) · Last reviewed commit: "Record the 2026-10-28 catalog refresh an..." · Reviewed by Greptile |
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.
Docs only. This records what changed in production on 2026-10-28.
Catalogs. goBILDA, ServoCity, AndyMark, and Pitsco were re-crawled locally at a slow pace (500 ms between pages, 1 s between Shopify feed pages, honouring robots.txt and Retry-After) and published through
catalog-load.tswith--expectHORS SKUs and--spot 20. Every spot check matched 20/20.Each previous generation is kept for a day of rollback. REV was not crawled.
REV cron (PR 55). The cron ran two full cycles in production. Cloudflare's CPU per run:
Every traced run ended
ok, but three went above 10 ms. Smaller steps barely help, because most of a step's cost is fixed per invocation, so the docs record this margin instead of claiming the steps fit.