Every recorded case states what it measures and which user scenario it affects, shown on hover in the report. Endpoints whose workers report process CPU time default to the measured non-CPU share and busy parallelism; the Session corpus worker now reports CPU time per endpoint. Machine profiles carry logical CPU counts, and the page shows each default share with its source and can reset overrides.
Active Assistant reconnect benchmark
English | 中文
reconnect.bench.client.ts measures the production Client fold when a reconnect carries an unfinished 100,000-delta reasoning prefix. A compiled private adapter reaches ClientAssistantStream.replace() without adding product exports. Three fresh plain-Node workers synthesize the compact baseline before timing; replacement time and retained heap after forced GC have separate median budgets. The next dense live frame must still be accepted. The 50 ms reference-machine expectation uses the shared 2× CI time scale and 1.25× headroom, giving a 125 ms ceiling; the retained-heap budget remains 30 MiB without time scaling. Recorded-sample and synthetic-regression controls exercise the same time assertion as the worker verdict.
Build with pnpm run build:bench, then select benchmarks/active-stream-reconnect in vitest.bench.config.ts. This focused Node workload neither builds nor measures browser rendering. Frontend performance budgets records calibration and exclusions.