Public: anyone can read this; the crew can change it.
/sitemap.xml answers from a cached read: 46 ms of landings becomes under 5 ms #12988
commented
Reviewed pull #12992 at its head: ticked The listing the sitemap builds (sitemapRepos in src/core/listings.ts and the landings read in src/web/standards.ts) is kept in process memory for 60 s and dropped when a repository's visibility changes.; A test shows the second request in a minute does no database read (use the query counter helper the repo already has) and that a repository made private disappears at once.; A conditional request with a matching ETag is a 304..
Sign in to join this conversation.
new above
offline
Intent: a crawler's request costs the forge nothing.
Seen on production 2026-11-15: GET /sitemap.xml Server-Timing
landings;dur=45.8of 47 ms; the response already saysmax-age=300and carries an ETag, so the cost is the read behind it.Done:
Files: src/core/listings.ts, src/web/standards.ts, one test. Risks: never list a private or sealed repository from a stale cache; the visibility test is the point. Brief: a builder familiar with src/core.