Codon VS Crystal benchmarks

Current benchmark data was generated on Mon Mar 31 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.15.1
codon 1-m.py 11ms 0.6ms 9.0MB 20ms 0ms codon 0.18.2

nbody

Input: 5000000

lang code time stddev peak-mem mem time(user) time(sys) compiler compiler/runtime
crystal 1.cr 344ms 1.7ms 3.1MB 333ms 0ms crystal 1.15.1
crystal 2.cr 345ms 2.2ms 3.1MB 337ms 0ms crystal 1.15.1
codon 1.py 1453ms 222ms 9.0MB 1763ms 0ms codon 0.18.2

Input: 500000

lang code time stddev peak-mem mem time(user) time(sys) compiler compiler/runtime
crystal 2.cr 38ms 0.8ms 3.1MB 30ms 0ms crystal 1.15.1
crystal 1.cr 39ms 1.3ms 3.1MB 30ms 0ms crystal 1.15.1
codon 1-m.py 174ms 3.5ms 8.9MB 483ms 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 298ms 0.7ms 8.1MB 290ms 0ms crystal 1.15.1
crystal 1.cr 416ms 4.8ms 42.3MB 403ms 0ms crystal 1.15.1
codon 1-m.py 419ms 4.2ms 47.6MB 723ms 0ms codon 0.18.2
codon 2.py 1525ms 10ms 100.8MB 1833ms 17ms codon 0.18.2

Input: 10

lang code time stddev peak-mem mem time(user) time(sys) compiler compiler/runtime
crystal 2.cr 77ms 1.4ms 4.4MB 70ms 0ms crystal 1.15.1
crystal 1.cr 89ms 2.5ms 13.0MB 80ms 0ms crystal 1.15.1
codon 1-m.py 127ms 2.6ms 18.5MB 433ms 0ms codon 0.18.2
codon 2-m.py 394ms 3.1ms 27.1MB 703ms 3ms codon 0.18.2