Codon VS Crystal benchmarks

Current benchmark data was generated on Mon May 19 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.1ms 2.9MB 0ms 0ms crystal 1.16.3
codon 1-m.py 12ms 0.7ms 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 344ms 1.1ms 3.3MB 333ms 0ms crystal 1.16.3
crystal 1.cr 345ms 2.6ms 3.3MB 337ms 0ms crystal 1.16.3
codon 1.py 1323ms 14ms 8.9MB 1630ms 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.2ms 3.3MB 30ms 0ms crystal 1.16.3
crystal 2.cr 39ms 1.3ms 3.3MB 30ms 0ms crystal 1.16.3
codon 1-m.py 177ms 3.9ms 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 347ms 2.0ms 8.2MB 340ms 0ms crystal 1.16.3
crystal 1.cr 445ms 17ms 42.9MB 430ms 0ms crystal 1.16.3
codon 1-m.py 455ms 9.2ms 47.7MB 757ms 0ms codon 0.18.2
codon 2.py 1561ms 6.3ms 100.8MB 1870ms 23ms codon 0.18.2

Input: 10

lang code time stddev peak-mem mem time(user) time(sys) compiler compiler/runtime
crystal 2.cr 88ms 2.0ms 4.4MB 80ms 0ms crystal 1.16.3
crystal 1.cr 91ms 3.3ms 13.2MB 83ms 0ms crystal 1.16.3
codon 1-m.py 126ms 3.4ms 18.4MB 433ms 0ms codon 0.18.2
codon 2-m.py 398ms 2.8ms 27.2MB 707ms 10ms codon 0.18.2