Artifact 852353a8cc53c4eb4e3b9e13d9e5ae88eb41c210683d3542e5ee0734c5479ab7:
- File
internal/web/web.go
-
2026-08-26 13:49:28
— part of check-in
[9bc994bada]
on branch ops-noise
— Dashboard: memoise the per-kind census; stop filing assets as renders
Two things the ops history surfaced.
GET /{$} serves two pages: the fleet for anonymous readers and the dashboard for signed-in ones. The census fix landed earlier addressed the fleet listing, so the spike a signed-in reader sees was never touched — the route pattern hid two different pages, which is the thing the drilldown exists to expose.
Measured cold across this fleet, EventKinds is 610ms of that page: a full covering-index scan of every artifact, per repository, for numbers that only move when a fold does. Memoised beside the other two, invalidated with them. TicketCounts measured 110ms and was left alone.
Asset requests are file serving, not renders. The browser asks for a sourcemap nobody ships, so /assets/datastar.js.map fell to the catch-all and filed a 404 against route '/' several times per page view. (user: dmestas, size: 688457) [annotate] [blame] [check-ins using]
- 2026-08-26 13:49:53 — part of check-in [7ec507a60e] on branch trunk — Accepted. The pattern hid two pages; the panel showed which one was slow once it stopped showing the pattern. (user: dmestas, size: 688457) [annotate] [blame] [check-ins using]
-
2026-08-26 13:49:28
— part of check-in
[9bc994bada]
on branch ops-noise
— Dashboard: memoise the per-kind census; stop filing assets as renders