Performance benchmarks

Tyravel ships a small benchmark harness for baseline throughput on three hot paths: HTTP responses, ORM reads, and view compilation.

Run locally

Build the workspace first, then:

npm run benchmark

JSON output for CI or dashboards:

npm run benchmark -- --json

Quick smoke mode (fewer samples):

BENCHMARK_QUICK=1 npm run benchmark

What is measured

Benchmark	What it exercises
http.json	In-process serve() handling GET /bench JSON responses with concurrent fetch
orm.select	Model.all() against 100 seeded rows in SQLite :memory:
view.compile	Compiling examples/hello-world/resources/views/welcome.tyr

Results are informational baselines, not competitive claims. Throughput varies with CPU, Node version, and concurrent load.

Interpreting results

• req/s and ops/s are rounded integers derived from total samples divided by elapsed milliseconds.
• Compare runs on the same machine and Node version when tracking regressions.
• Use the observability cookbook for production latency and saturation signals — benchmarks do not replace real traffic profiling.

CI trend artifacts

On every push to main, the Benchmarks workflow runs quick-mode benchmarks (BENCHMARK_QUICK=1) and uploads a JSON artifact named benchmark-report-<sha>. Download artifacts from the workflow run to compare throughput over time.

The job is informational only — it does not fail on regressions. Use it to spot large swings before they reach production profiling.

Expected ranges (Node 26, Linux CI, quick mode)

GitHub-hosted ubuntu-latest runners are noisy; treat these as ballpark ranges, not pass/fail gates:

Benchmark	Typical range
http.json	800 – 3,000 req/s
orm.select	5,000 – 20,000 ops/s
view.compile	20,000 – 60,000 ops/s

Full local runs (BENCHMARK_QUICK=0) use larger sample sizes and usually report higher throughput on a dedicated machine.

Related

• Deployment — horizontal scaling and worker sizing
• Observability cookbook — health probes, structured logs, queue failure signals
• Testing — feature and integration coverage alongside perf baselines