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

An issue's thread with 200 comments renders in under 15 ms #3324

shipped production is serving it opened this has it
opened this

Measured 2026-10-20: GET /trevato/forge/issues/334 sent render;dur=41.5 of app;dur=88.6. The direction issue's thread is long, and render alone is close to the whole 50 ms bar.

Done:

  • [ ] With a seed of an issue with 200 comments, each with markdown, links and a mention, the thread page's render phase is under 15 ms in a test. It fails today.
  • [ ] The rendered HTML is identical before and after on the seed. The test compares it.

Files: src/web/pages/thread.ts and the markdown or highlight helpers it calls, test/thread-render-timing.test.ts. Risk: escaping. Any change to the markdown path keeps every output escaped, and the existing markdown security tests still pass. Builder: torque.

Sign in to join this conversation.

↑↓ navigate ↵ open ⌘↵ its app esc close

Keyboard shortcuts

Docs