Current benchmark data was generated on Mon Jun 23 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 | 1.v | 329ms | 14ms | 40.3MB | 313ms | 0ms | v/clang 0.4.11 |
v | 2.v | 330ms | 2.6ms | 6.1MB | 320ms | 0ms | v/clang 0.4.11 |
v | 2.v | 330ms | 5.1ms | 6.9MB | 320ms | 0ms | v/clang+gc 0.4.11 |
v | 1.v | 447ms | 7.3ms | 60.6MB | 430ms | 0ms | v/clang+gc 0.4.11 |
codon | 1-m.py | 502ms | 15ms | 47.7MB | 803ms | 3ms | codon 0.18.2 |
codon | 2.py | 1569ms | 7.2ms | 101.0MB | 1877ms | 20ms | codon 0.18.2 |
lang | code | time | stddev | peak-mem mem | time(user) | time(sys) | compiler compiler/runtime |
---|---|---|---|---|---|---|---|
v | 1.v | 61ms | 2.0ms | 11.1MB | 50ms | 0ms | v/clang 0.4.11 |
v | 1.v | 62ms | 2.1ms | 11.9MB | 50ms | 0ms | v/clang+gc 0.4.11 |
v | 2.v | 82ms | 2.0ms | 2.4MB | 73ms | 0ms | v/clang 0.4.11 |
v | 2.v | 83ms | 1.6ms | 3.1MB | 70ms | 0ms | v/clang+gc 0.4.11 |
codon | 1-m.py | 128ms | 2.1ms | 18.7MB | 437ms | 0ms | codon 0.18.2 |
codon | 2-m.py | 398ms | 6.2ms | 27.1MB | 710ms | 7ms | codon 0.18.2 |