Codon VS Nim benchmarks

Current benchmark data was generated on Sun Jun 01 2025, full log can be found HERE

CONTRIBUTIONS are WELCOME!

[x86_64][4 cores] AMD EPYC 7763 64-Core Processor (Model 1)

* -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.)

helloworld

Input: QwQ

lang code time stddev peak-mem mem time(user) time(sys) compiler compiler/runtime
nim 1.nim 0.9ms 0.0ms 1.5MB 0ms 0ms nim 2.2.4
nim 1.nim 1.1ms 0.0ms 1.9MB 0ms 0ms nim/clang 2.2.4
codon 1-m.py 11ms 0.4ms 8.8MB 20ms 0ms codon 0.18.2

nbody

Input: 5000000

lang code time stddev peak-mem mem time(user) time(sys) compiler compiler/runtime
nim 2.nim 318ms 0.5ms 1.8MB 310ms 0ms nim 2.2.4
nim 2.nim 344ms 2.8ms 2.0MB 337ms 0ms nim/clang 2.2.4
codon 1.py 1352ms 60ms 9.1MB 1657ms 0ms codon 0.18.2

Input: 500000

lang code time stddev peak-mem mem time(user) time(sys) compiler compiler/runtime
nim 2.nim 34ms 0.6ms 1.8MB 30ms 0ms nim 2.2.4
nim 2.nim 37ms 1.1ms 2.0MB 30ms 0ms nim/clang 2.2.4
codon 1-m.py 175ms 4.2ms 8.8MB 487ms 0ms codon 0.18.2

nsieve

Input: 12

lang code time stddev peak-mem mem time(user) time(sys) compiler compiler/runtime
nim 1.nim 264ms 6.1ms 41.5MB 250ms 0ms nim 2.2.4
nim 1.nim 316ms 7.7ms 41.8MB 300ms 0ms nim/clang 2.2.4
codon 1-m.py 444ms 8.1ms 67.3MB 743ms 7ms codon 0.18.2
codon 2.py 1520ms 13ms 100.8MB 1830ms 17ms codon 0.18.2

Input: 10

lang code time stddev peak-mem mem time(user) time(sys) compiler compiler/runtime
nim 1.nim 52ms 2.1ms 11.5MB 47ms 0ms nim 2.2.4
nim 1.nim 63ms 5.6ms 11.8MB 53ms 0ms nim/clang 2.2.4
codon 1-m.py 128ms 1.7ms 18.5MB 437ms 0ms codon 0.18.2
codon 2-m.py 392ms 4.2ms 27.4MB 703ms 7ms codon 0.18.2