Benchmarks
How fast is Zeno?
Six programs, written once in Zeno, C, Rust and Python, doing the same steps. Every time was measured, and counts only if the program printed exactly what C printed.
Before and after
Drag to compare. Before is the first run, when the collector kept every block in one table that it sorted on each collection. Now it keeps them in pages, and a program can choose memory owned instead (decision 22.5).
The program in other languages
New in 0.5: zeno build --target writes a program in another language. Here each one is run with that language's own tools, at the small sizes, so the times include starting Node, the JVM or .NET. Every cell is a time divided by the time of the same program in C. Smaller is faster. From the record of 0.5.1.
| Average | Function calls | A tight loop | Sorting a list | Building text | Many small objects | Floating point | |
|---|---|---|---|---|---|---|---|
| --target javabuilt by javac | 17× Con average | 37× C | 16× C | 11× C | 9× C | 5× C | 79× C |
| --target jsin Node | 23× Con average | 28× C | 45× C | 10× C | 6× C | 10× C | 180× C |
| --target cppbuilt by g++ -O2 | 32× Con average | 46× C | 19× C | 14× C | 18× C | 21× C | 215× C |
| --target gobuilt by go | 35× Con average | 49× C | 55× C | 17× C | 10× C | 16× C | 231× C |
| --target rustbuilt by rustc -O | 43× Con average | 83× C | 65× C | 19× C | 12× C | 23× C | 220× C |
| --target wasmin Node | 58× Con average | 117× C | 98× C | 29× C | 14× C | 24× C | 352× C |
| zeno run --vm | 69× Con average | 141× C | 88× C | 34× C | 18× C | 45× C | 313× C |
| --target csbuilt by dotnet | 78× Con average | 175× C | 116× C | 40× C | 19× C | 30× C | 472× C |
| --target phpin PHP | 152× Con average | 390× C | 261× C | 89× C | 12× C | 90× C | 1267× C |
| --target pyin Python 3 | 281× Con average | 594× C | 595× C | 189× C | 17× C | 172× C | 2478× C |
A written program carries Zeno's rules with it, so it does what zeno run does, checks and all, in a language that was not built for them. zeno run --vm is in the table as a guide. The targets are for reading, keeping and running a program where Zeno is not; for speed, zeno build --fast is the way.
Version by version
Each release keeps a record of its times, made with bench/record.py. Every cell is a time divided by the time of C (or of Python, for the ways that interpret) in the same run, so records made on different days still line up. Smaller is faster.
Five ways to run a program
The same file, run five ways. Each step down does more work before the program starts, and less while it runs.
zeno runWalks the syntax treeEvery step looks at a node of the tree and decides what it means. Simple, exact errors, and slow.
zeno run --vmRuns bytecodeThe tree is turned into a flat list of small instructions once, then a loop runs them. Two to three times faster.
zeno buildCompiles to CThe program becomes C and then machine code. Each value is found by a garbage collector, and each
+checks for overflow.--release --ownedNo collector, no overflow checksEach value has one owner and is freed at a line you can point to, from a pool that hands out a block in a few instructions.
--fast --ownedNo checks a correct program never failsNo index checks either, a float divided by zero is infinity, and the C compiler tries its hardest. As fast as C, and as unforgiving.
What the numbers say
malloc and free.+, which --release drops, as Rust's release builds do. Index checks stay.--fast runs the instructions C runsIt tells the C compiler what a C program tells it: a whole number does not overflow. On the loop of whole numbers it runs 300.27 million instructions where C runs 300.26 million (decision 23.6).for ch in text walks the text without making a list of it, and a field a function never writes is read once, as a C programmer would by hand (decisions 22.7 and 22.8).Choose once, in zeno.package, with memory owned, or for one build with zeno build --owned. See Choosing how memory is freed.
How it was measured
Wall-clock time of the whole program, best of three. Compiled programs at full size, interpreted ones at a tenth of it. Intel(R) Xeon(R) Processor @ 2.10GHz, 4 cores, Linux, on 2026-11-16. zeno 0.4.0, cc 13.3.0 with -O2, rustc 1.97.0 with -C opt-level=3, Python 3.13.18.
The programs and the script are in bench/. The numbers on this page are in data.json.
cargo build --release
python3 bench/run.py --size big --engines c,rust,zeno,zeno-release,zeno-owned