Current benchmark data was generated on Tue Mar 25 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.)
code | time | stddev | peak-mem mem | time(user) | time(sys) | compiler compiler/runtime |
---|---|---|---|---|---|---|
1-m.py | 11ms | 0.7ms | 8.6MB | 20ms | 0ms | codon 0.18.2 |
code | time | stddev | peak-mem mem | time(user) | time(sys) | compiler compiler/runtime |
---|---|---|---|---|---|---|
1.py | 1322ms | 1.2ms | 8.8MB | 1630ms | 0ms | codon 0.18.2 |
code | time | stddev | peak-mem mem | time(user) | time(sys) | compiler compiler/runtime |
---|---|---|---|---|---|---|
1-m.py | 176ms | 3.4ms | 9.0MB | 487ms | 0ms | codon 0.18.2 |