Current benchmark data was generated on Mon Mar 31 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 | 290ms | 2.3ms | 40.2MB | 273ms | 0ms | v/clang 0.4.10 |
v | 1.v | 303ms | 2.9ms | 41.1MB | 290ms | 0ms | v/clang+gc 0.4.10 |
v | 2.v | 327ms | 1.3ms | 6.9MB | 320ms | 0ms | v/clang+gc 0.4.10 |
v | 2.v | 332ms | 2.2ms | 6.1MB | 320ms | 0ms | v/clang 0.4.10 |
codon | 1-m.py | 419ms | 4.2ms | 47.6MB | 723ms | 0ms | codon 0.18.2 |
codon | 2.py | 1525ms | 10ms | 100.8MB | 1833ms | 17ms | codon 0.18.2 |
lang | code | time | stddev | peak-mem mem | time(user) | time(sys) | compiler compiler/runtime |
---|---|---|---|---|---|---|---|
v | 1.v | 59ms | 1.2ms | 11.0MB | 50ms | 0ms | v/clang 0.4.10 |
v | 1.v | 60ms | 1.5ms | 11.7MB | 50ms | 0ms | v/clang+gc 0.4.10 |
v | 2.v | 81ms | 0.9ms | 3.1MB | 70ms | 0ms | v/clang+gc 0.4.10 |
v | 2.v | 83ms | 2.5ms | 2.4MB | 77ms | 0ms | v/clang 0.4.10 |
codon | 1-m.py | 127ms | 2.6ms | 18.5MB | 433ms | 0ms | codon 0.18.2 |
codon | 2-m.py | 394ms | 3.1ms | 27.1MB | 703ms | 3ms | codon 0.18.2 |