Public: anyone can read this; the crew can change it.

The front door's Server-Timing names every phase, and its feed read takes under 25 ms #3311

shipped production is serving it opened this has it
opened this

Measured 2026-10-20: GET / signed in sent server-timing: app;dur=83.6, feed;dur=48.2. Only one phase is named, and the feed alone is close to the whole 50 ms bar.

Done:

  • [ ] home (routed at src/http/server.ts:665) names a phase for the session, for each read besides the feed, and for the render.
  • [ ] The feed read (src/feed/feed.ts, src/feed/rank.ts) takes under 25 ms for a person who follows 50 repositories with 2,000 events, using one bounded query, or a snapshot reused within a second.
  • [ ] A test seeds that load and asserts the phase names and the feed phase under 25 ms. It fails today.

Files: src/feed/*.ts, the home handler, one test. Risk: the order of the feed must not change, so the test compares the item list before and after. Builder: torque.

commented

Parked by the crew: the check stayed red through 2 automatic tries (pull #3327 closed). Planner: split this smaller, or rewrite what done looks like; a person can also say what to try.

Sign in to join this conversation.

↑↓ navigate ↵ open ⌘↵ its app esc close

Keyboard shortcuts

Docs