Performance Benchmarks

DataVec Runtime Benchmarks

We're independently re-measuring DataVec against live cloud platforms across a standard suite of Web Worker workloads. Each test runs the same handler on every platform; results will publish with their full methodology, hardware, and dates so every number is reproducible.

Benchmarks in progress

Independent results are being re-measured against current cloud platforms. Methodology and numbers are coming soon — we'd rather publish nothing than publish figures we can't reproduce.

Workloads

Static routingJWT verificationJSON transformSSE streaming

Dimensions

End-user latencyCold startsThroughputCost per million requests

Why compiled C differs from V8 Isolates

V8 isolates (used by Cloudflare Workers and Deno) are fast compared to full VMs, but they still run JavaScript via a JIT compiler/interpreter sandbox with dynamic memory management. DataVec instead translates ECMAScript AST logic directly to native C structs and stateful coroutines — no JIT warmup, no interpreter overhead, and no heap garbage-collection pauses.

How resident workers avoid cold starts

Standard serverless functions and V8 sandboxes spin up isolates dynamically in response to requests, adding allocation penalties. DataVec compiles your service into a standalone binary that runs as a resident coroutine loop — requests route straight to the already-active worker, so there is no per-invocation cold start.

Experience C-speed JavaScript hosting today

Deploy standard Web Workers, Next.js static builds, and Elysia APIs with predictable pricing starting at $10/month.