Codon VS Nim benchmarks

Current benchmark data was generated on Mon Jun 23 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 1.0ms 0.0ms 1.6MB 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 12ms 0.9ms 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 321ms 2.4ms 1.8MB 310ms 0ms nim 2.2.4
nim 2.nim 344ms 1.2ms 1.9MB 330ms 0ms nim/clang 2.2.4
codon 1.py 1453ms 224ms 8.8MB 1763ms 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 38ms 1.4ms 2.0MB 30ms 0ms nim/clang 2.2.4
codon 1-m.py 175ms 4.0ms 8.8MB 483ms 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 306ms 36ms 41.5MB 297ms 0ms nim 2.2.4
nim 1.nim 334ms 13ms 41.8MB 323ms 0ms nim/clang 2.2.4
codon 1-m.py 502ms 15ms 47.7MB 803ms 3ms codon 0.18.2
codon 2.py 1569ms 7.2ms 101.0MB 1877ms 20ms codon 0.18.2

Input: 10

lang code time stddev peak-mem mem time(user) time(sys) compiler compiler/runtime
nim 1.nim 51ms 1.1ms 11.5MB 40ms 0ms nim 2.2.4
nim 1.nim 67ms 7.6ms 11.8MB 60ms 0ms nim/clang 2.2.4
codon 1-m.py 128ms 2.1ms 18.7MB 437ms 0ms codon 0.18.2
codon 2-m.py 398ms 6.2ms 27.1MB 710ms 7ms codon 0.18.2