Programming Language and compiler
Benchmarks

Results for 38 of 40 languages from this run on actest1.

Unavailable in this run: Hack, Lisp. Follow the run link for failure details.

All Pony benchmarks

Current benchmark data was generated on Sun Sep 27 2026, full log can be found HERE

CONTRIBUTIONS are WELCOME!

[x86_64][4 cores] Intel(R) Core(TM) i7-3687U CPU @ 2.10GHz (Model 58)

* -m in a file name stands for multi-threading or multi-processing

* -i in a file name stands for direct intrinsics usage. (Usage of simd intrinsics via libraries is not counted)

* -ffi in a file name stands for non-stdlib FFI usage

* (You may find time < time(user) + time(sys) for some non-parallelized programs, the overhead is from GC or JIT compiler, which are allowed to take advantage of multi-cores as that's more close to real-world scenarios.)

binarytrees

Input: 18

code time stddev peak-mem mem time(user) time(sys) compiler compiler/runtime
1.pony 2171ms 7.7ms 2203.4MB 1560ms 487ms ponyc 0.73.0

Input: 15

code time stddev peak-mem mem time(user) time(sys) compiler compiler/runtime
1.pony 352ms 12ms 220.3MB 167ms 33ms ponyc 0.73.0

helloworld

Input: QwQ

code time stddev peak-mem mem time(user) time(sys) compiler compiler/runtime
1.pony 35ms 0.3ms 14.5MB 0ms 0ms ponyc 0.73.0

lru

Input: 1000 1000000

code time stddev peak-mem mem time(user) time(sys) compiler compiler/runtime
1.pony 44443ms 481ms 76.4MB 44053ms 20ms ponyc 0.73.0

Input: 1000 3000000

code time stddev peak-mem mem time(user) time(sys) compiler compiler/runtime
1.pony timeout (120s) — — — — ponyc 0.73.0

Input: 100 500000

code time stddev peak-mem mem time(user) time(sys) compiler compiler/runtime
1.pony 2657ms 0.2ms 44.4MB 2273ms 10ms ponyc 0.73.0

nbody

Input: 5000000

code time stddev peak-mem mem time(user) time(sys) compiler compiler/runtime
1.pony 1157ms 0.2ms 16.5MB 700ms 7ms ponyc 0.73.0

Input: 500000

code time stddev peak-mem mem time(user) time(sys) compiler compiler/runtime
1.pony 149ms 46ms 16.5MB 73ms 3ms ponyc 0.73.0