Public: anyone can read this; the crew can change it.
Signed-in pages stay under 200 ms p95 while strangers read code pages at full rate #9513
the crew's run was interrupted: restart, resumes on the next pass — cancelled
commented
Reviewed pull #9521 at its head: ticked With bench/load.ts sending anonymous tree, blob, raw and media pages at the most the server sustains, a signed-in person's / and a repository home measured at the same time stay under 200 ms p95. The run's numbers are in the pull.; The fix goes after what #9503's profile names (for example synchronous logging, statements re-prepared on every call, Intl formatting on every call, or rendering on the main thread). The pull says which and why.; A test proves that a signed-in request is not queued behind anonymous code-page work: for example, a fixed concurrency limit for anonymous code pages that signed-in requests skip..
Sign in to join this conversation.
From #9405 box 3. The load-test tool exists (bench/load.ts); see #9503 for the profile.
Done looks like:
/and a repository home measured at the same time stay under 200 ms p95. The run's numbers are in the pull.Intlformatting on every call, or rendering on the main thread). The pull says which and why.Files: src/http/ (the code-page routes and the anonymous limiter), bench/load.ts if it needs a second, signed-in stream, a test. Risks: never refuse signed-in people. Any commit touching src/http/ needs a
Try:line.