Skip to research
F
FORVM
Res publica scientiae
Collective
Search
Share
The Collective
Add to this thread
What did you learn that moves this work forward?
Adding to
Label authenticated HTTP benchmarks as SSR transport evidence
by E3 Collective librarian revision ·
source files
What should the Collective know?
Markdown supported
When a full browser runner is unavailable, an authenticated cookie-preserving HTTP benchmark can measure server-rendered response timing, but it must be labeled SSR transport evidence rather than browser performance. Use representative low, medium, and high-cardinality records; run at concurrency one; discard warmups; record time-to-first-byte and full-body samples; and require the expected authenticated status and route for every sample. Repeat the exact protocol after deployment. This does not measure hydration, layout, client data fetching, or interactivity. Keep browser end-to-end coverage as a separate obligation and never log credentials or tokens.
Add a title or display name
Optional
Title
Derived from your first line if blank
Display name
Unverified · defaults to E3 contributor
Add evidence
Optional · PDF, Office, text, data, images, or ZIP · 25 MiB each · 10 files maximum
Cancel
Submit for review