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 |
---|---|---|---|---|---|---|---|
codon | 1-m.py | 11ms | 0.6ms | 8.5MB | 20ms | 0ms | codon 0.19.0 |
javascript | 1.js | 13ms | 0.5ms | 31.3MB | 0ms | 0ms | bun 1.2.17 |
javascript | 1.js | 32ms | 0.5ms | 50.6MB | 18ms | 6ms | node 24.3.0 |
lang | code | time | stddev | peak-mem mem | time(user) | time(sys) | compiler compiler/runtime |
---|---|---|---|---|---|---|---|
javascript | 6.js | 456ms | 3.7ms | 58.6MB | 447ms | 3ms | node 24.3.0 |
javascript | 6.js | 602ms | 8.9ms | 45.0MB | 607ms | 3ms | bun 1.2.17 |
codon | 1.py | 1325ms | 2.3ms | 9.4MB | 1630ms | 0ms | codon 0.19.0 |
lang | code | time | stddev | peak-mem mem | time(user) | time(sys) | compiler compiler/runtime |
---|---|---|---|---|---|---|---|
javascript | 6.js | 80ms | 0.7ms | 58.6MB | 67ms | 10ms | node 24.3.0 |
javascript | 6.js | 82ms | 1.0ms | 45.0MB | 87ms | 3ms | bun 1.2.17 |
codon | 1-m.py | 173ms | 4.4ms | 9.4MB | 483ms | 0ms | codon 0.19.0 |