Current benchmark data was generated on Sun Jul 13 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 | 321ms | 15ms | 40.3MB | 307ms | 0ms | v/clang 0.4.11 |
| v | 1.v | 323ms | 7.3ms | 41.2MB | 310ms | 0ms | v/clang+gc 0.4.11 |
| v | 2.v | 329ms | 1.3ms | 6.1MB | 320ms | 0ms | v/clang 0.4.11 |
| v | 2.v | 331ms | 4.8ms | 6.9MB | 323ms | 0ms | v/clang+gc 0.4.11 |
| codon | 1-m.py | 410ms | 9.1ms | 48.4MB | 713ms | 3ms | codon 0.19.0 |
| codon | 2.py | 903ms | 4.6ms | 100.8MB | 1207ms | 20ms | codon 0.19.0 |
| lang | code | time | stddev | peak-mem mem | time(user) | time(sys) | compiler compiler/runtime |
|---|---|---|---|---|---|---|---|
| v | 1.v | 61ms | 2.9ms | 11.9MB | 50ms | 0ms | v/clang+gc 0.4.11 |
| v | 1.v | 65ms | 0.6ms | 11.0MB | 57ms | 0ms | v/clang 0.4.11 |
| v | 2.v | 82ms | 1.5ms | 3.1MB | 73ms | 0ms | v/clang+gc 0.4.11 |
| v | 2.v | 83ms | 2.1ms | 2.4MB | 73ms | 0ms | v/clang 0.4.11 |
| codon | 1-m.py | 118ms | 3.1ms | 18.9MB | 423ms | 0ms | codon 0.19.0 |
| codon | 2-m.py | 236ms | 3.0ms | 27.6MB | 540ms | 3ms | codon 0.19.0 |