Current benchmark data was generated on Thu Feb 01 2024, 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.py | 4.5ms | 0.8ms | 7.2MB | 0ms | 0ms | codon 0.16.3 |
code | time | stddev | peak-mem mem | time(user) | time(sys) | compiler compiler/runtime |
---|---|---|---|---|---|---|
1.py | 1295ms | 1.9ms | 7.7MB | 1287ms | 0ms | codon 0.16.3 |
code | time | stddev | peak-mem mem | time(user) | time(sys) | compiler compiler/runtime |
---|---|---|---|---|---|---|
1.py | 140ms | 2.4ms | 5.8MB | 127ms | 0ms | codon 0.16.3 |