How krausest/js-framework-benchmark works
js-framework-benchmark compares keyed and non-keyed implementations by running browser workloads and reporting timings, memory, startup, Lighthouse, and transfer metrics. The principal workflow is to serve a framework implementation, execute benchmark iterations, and inspect the generated results. The server also exposes framework metadata, static assets, CSP checks, and response-size controls. The README documents the benchmark stages and metrics; sampled source confirms server routing and selected implementation behavior, but the benchmark driver internals and many framework implementations were not inspected.
Main entry points: timeline.ts Browser workloads · app.ts HTTP server · staticRouter.ts Static assets · App.tsx Benchmark index
Components 18
Benchmark web app
- Benchmark index
webdriver-ts-results/src/App.tsx - Result tables
webdriver-ts-results/src/components/ResultTable/ResultTable.tsx
Framework implementations
- Keyed variants
frameworks/keyed - Non-keyed variants
frameworks/non-keyed - Broken variants
broken-frameworks
Benchmark execution
- Browser workloads
webdriver-ts/src/timeline.ts - Row operations
webdriver-ts/src/timeline.ts - Memory metrics
webdriver-ts/src/timeline.ts - Startup and Lighthouse
webdriver-ts/src/timeline.ts - Benchmark results
webdriver-ts-results
Local server
- HTTP server
server/app.ts - Framework routes
server/src/frameworks/frameworksControllers.ts - Framework metadata
server/src/frameworks/frameworksServices.ts - Static assets
server/src/static/staticRouter.ts - CSP reporting
server/src/csp/cspControllers.ts - Response size
server/src/responseSize/responseSizeController.ts - Size accounting
server/src/responseSize/responseSizeDecorator.ts
Other components
- Benchmark user
Connections 20
- Benchmark user → Benchmark index: reviews results
- Benchmark user → Browser workloads: runs benchmarks
- Benchmark index → Result tables: renders tables
webdriver-ts-results/src/App.tsx - Browser workloads → Keyed variants: loads implementations
- Browser workloads → Non-keyed variants: loads implementations
- Browser workloads → Broken variants: may test
- Browser workloads → Row operations: measures operations
- Browser workloads → Memory metrics: measures memory
- Browser workloads → Startup and Lighthouse: measures startup
- Browser workloads → Benchmark results: produces results
- Benchmark user → HTTP server: starts locally
- HTTP server → Framework routes: registers routes
server/app.ts - Framework routes → Framework metadata: loads metadata
server/src/frameworks/frameworksControllers.ts - HTTP server → Static assets: registers routes
server/app.ts - Static assets → Keyed variants: serves files
server/src/static/staticRouter.ts - Static assets → Non-keyed variants: serves files
server/src/static/staticRouter.ts - HTTP server → CSP reporting: registers routes
server/app.ts - HTTP server → Response size: registers routes
server/app.ts - HTTP server → Size accounting: configures accounting
server/app.ts - Response size → Size accounting: controls totals