Artifact 7c9e5e66c8da4c32dd40fe69bc3136cde9499882664a56feaa3351d398dadd44:
- File
internal/obs/route_test.go
-
2026-08-25 21:45:00
— part of check-in
[bb6ec6b896]
on branch ops-drill
— ops: open a route up — which repository, and which store calls
The panel finds a slow route; this says why. Two things the roll-up cannot show.
WHICH REPOSITORY. A route pattern folds pikchr and tcl into one line, and repository size is the dominant cost on this fleet — GET /r/{repo} at 420ms could be either, and the two differ by orders of magnitude.
WHICH CALLS. Each recent request is listed with the store calls it made, in the order it made them, and what they cost together. A request with no calls listed spent its time somewhere else, which is itself the answer when the store is not to blame.
Reads the same rings the panels read, so a request that has aged out simply is not there. That is the honest limit of a snapshot: this answers what a slow request just did, not what happened yesterday. (user: dmestas, size: 3299) [annotate] [blame] [check-ins using]
- 2026-08-25 21:53:53 — part of check-in [7059271e59] on branch trunk — Accepted. It can now say which repo and which calls — which is the difference between finding a slow route and fixing one. (user: dmestas, size: 3299) [annotate] [blame] [check-ins using]
-
2026-08-25 21:45:00
— part of check-in
[bb6ec6b896]
on branch ops-drill
— ops: open a route up — which repository, and which store calls