Current benchmark data was generated on Tue Jul 01 2025, full log can be found HERE
CONTRIBUTIONS are WELCOME!
* -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.)
| lang | code | time | stddev | peak-mem mem | time(user) | time(sys) | compiler compiler/runtime |
|---|---|---|---|---|---|---|---|
| v | 2.v | 330ms | 4.8ms | 6.9MB | 323ms | 0ms | v/clang+gc 0.4.11 |
| v | 2.v | 332ms | 2.9ms | 6.1MB | 323ms | 0ms | v/clang 0.4.11 |
| v | 1.v | 341ms | 4.3ms | 40.3MB | 323ms | 0ms | v/clang 0.4.11 |
| v | 1.v | 346ms | 3.1ms | 41.2MB | 337ms | 0ms | v/clang+gc 0.4.11 |
| codon | 1-m.py | 409ms | 6.0ms | 48.6MB | 697ms | 3ms | codon 0.19.0 |
| codon | 2.py | 913ms | 1.4ms | 100.8MB | 1220ms | 23ms | codon 0.19.0 |
| lang | code | time | stddev | peak-mem mem | time(user) | time(sys) | compiler compiler/runtime |
|---|---|---|---|---|---|---|---|
| v | 1.v | 61ms | 0.8ms | 11.1MB | 50ms | 0ms | v/clang 0.4.11 |
| v | 1.v | 63ms | 1.7ms | 19.0MB | 50ms | 0ms | v/clang+gc 0.4.11 |
| v | 2.v | 80ms | 0.4ms | 3.1MB | 70ms | 0ms | v/clang+gc 0.4.11 |
| v | 2.v | 83ms | 2.0ms | 2.4MB | 70ms | 0ms | v/clang 0.4.11 |
| codon | 1-m.py | 117ms | 2.3ms | 19.4MB | 427ms | 0ms | codon 0.19.0 |
| codon | 2-m.py | 233ms | 3.4ms | 27.7MB | 543ms | 7ms | codon 0.19.0 |