You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
demo(benchmark-react): Use response-size-based network simulation delays (#3810)
Replace fixed per-method network delays with a formula: 40ms base latency +
2ms per record in the response. This more realistically models how network
time scales with payload size, naturally penalizing large list refetches
relative to normalized cache propagation.
Made-with: Cursor
Median ops/s per scenario; range is approximate 95% CI margin from the runner (`stats.ts`). **Network simulation**applies the per-RPC delays in `bench/scenarios.ts` (`NETWORK_SIM_DELAYS`, e.g. `fetchIssueList` 80 ms, `updateUser` 50 ms) so list refetches after an author update pay extra latency compared to normalized propagation.
66
+
Median ops/s per scenario; range is approximate 95% CI margin from the runner (`stats.ts`). **Network simulation**uses response-size-based delays (`NETWORK_SIM_CONFIG`in `bench/scenarios.ts`: 40 ms base latency + 1 ms per 20 records) so list refetches after an author update pay extra latency compared to normalized propagation.
67
67
68
-
Run: **2026-03-21**, Linux (WSL2), `yarn build:benchmark-react`, static preview + `env -u CI npx tsx bench/runner.ts --network-sim true` (all libraries; memory scenarios not included). Numbers are **machine-specific**; use them for relative comparison between libraries, not as absolutes.
68
+
Run: **2026-03-22**, Linux (WSL2), `yarn build:benchmark-react`, static preview + `env -u CI npx tsx bench/runner.ts --network-sim true` (all libraries; memory scenarios not included). Numbers are **machine-specific**; use them for relative comparison between libraries, not as absolutes.
0 commit comments