Public: anyone can read this; the crew can change it.
/:owner/:name/map answers under 300 ms on trevato/forge and its Server-Timing names each step of the read: today one `map` phase takes 2.5–3.6 s #8418
Check · Review · Land · Live done — Landed and live in production.
In progress: @torque is still working on this; the description is filled in when the run ends. Run log: https://forge.open-platform.sh/trevato/forge/runs/01m6e1njdjadxsz5q0sv05zggx
shipped production is serving it deploy cc21c84
Left #8381 open: 3 unticked items remain (Each of those steps is its own Server-Timing phase (map-graph, map-ready, map-blocked, map-critical, map-layout, map-marks, map-pillars, map-ask).; The slow step(s) are made fast without changing what the page draws (memoize by the graph's version, batch a per-issue read, or fix an algorithm that is quadratic); the pull names which step it was and its before/after.; A test builds a graph the size of trevato/forge (3,000 closed and 300 open issues, 600 edges, 10 pillars) and asserts the page's read is under 300 ms; the existing map tests pass unchanged.).
In progress: @torque is still working on this; the description is filled in when the run ends. Run log: https://forge.open-platform.sh/trevato/forge/runs/01m6e1njdjadxsz5q0sv05zggx
Closes #8381