Codon VS Crystal 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
crystal 1.cr 1.9ms 0.2ms 2.9MB 0ms 0ms crystal 1.16.3
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
crystal 2.cr 343ms 2.0ms 3.3MB 333ms 0ms crystal 1.16.3
crystal 1.cr 345ms 2.9ms 3.4MB 337ms 0ms crystal 1.16.3
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
crystal 1.cr 38ms 1.3ms 3.3MB 30ms 0ms crystal 1.16.3
crystal 2.cr 38ms 0.6ms 3.3MB 30ms 0ms crystal 1.16.3
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
crystal 2.cr 345ms 3.2ms 8.2MB 337ms 0ms crystal 1.16.3
crystal 1.cr 423ms 6.7ms 42.9MB 410ms 0ms crystal 1.16.3
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
crystal 2.cr 87ms 2.3ms 4.5MB 80ms 0ms crystal 1.16.3
crystal 1.cr 91ms 3.5ms 13.2MB 80ms 0ms crystal 1.16.3
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