ws-orpc

oRPC WebSocket Runtime Benchmark

• Evaluates the performance of oRPC's RPC runtime over WebSocket on a project with 6 procedures and 3 routers.
• Uses Standard Schema instead of a specific library like Zod so the results reflect oRPC's performance without external influences.
• Since autocannon only supports HTTP, load is generated by a custom client (scripts/client.ts): 10 concurrent connections, each running one request at a time through the real oRPC WebSocket client for 20 seconds — mirroring autocannon's defaults in the HTTP benchmarks.
• Comparable to the other benchmarks in the ws group: ws-orpc, ws-trpc.
• Every run profiles the server with Clinic.js Doctor and overwrites the committed report at .clinic/report.clinic-doctor.html.

How to run

pnpm bench

Latest Result

oRPC 2.0.0-beta.26 - 2026-08-09

Running 20s WebSocket test @ ws://127.0.0.1:3000
10 connections

Latency: avg=0.41 ms stdev=0.41 ms p50=0.39 ms p97.5=0.81 ms p99=0.95 ms max=83.73 ms
Req/Sec: avg=24,126 stdev=2,201 min=14,637 max=25,184

482,511 requests in 20.00s

Clinic Doctor summary (full report, view in browser):

• CPU usage: ~104% on average (max 367%)
• Memory (RSS): 71 MB - 110 MB
• Event loop delay: 0.02 ms on average (max 3.13 ms)
• Detected issues: none

Run on:

CPU: Intel(R) Core(TM) i5-8265U CPU @ 1.60GHz (8 cores)
Memory: 7238 MB
OS: Linux 7.0.0-29-generic x64
Node: 24.18.1
pnpm: 11.17.0