Codon VS Crystal benchmarks

Current benchmark data was generated on Sun Jan 29 2023, full log can be found HERE

CONTRIBUTIONS are WELCOME!

[x86_64][2 cores] Intel(R) Xeon(R) Platinum 8370C CPU @ 2.80GHz (Model 106)

* -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 2.2ms 0.7ms 2.9MB 0ms 0ms crystal 1.7.2
codon 1.py 4.1ms 0.8ms 5.3MB 0ms 0ms codon 0.15.4

nbody

Input: 5000000

lang code time stddev peak-mem mem time(user) time(sys) compiler compiler/runtime
crystal 1.cr 514ms 1.1ms 3.0MB 500ms 0ms crystal 1.7.2
crystal 2.cr 535ms 0.2ms 2.9MB 530ms 0ms crystal 1.7.2
codon 1.py 1947ms 23ms 5.3MB 1933ms 0ms codon 0.15.4

Input: 500000

lang code time stddev peak-mem mem time(user) time(sys) compiler compiler/runtime
crystal 1.cr 54ms 0.2ms 2.9MB 43ms 0ms crystal 1.7.2
crystal 2.cr 56ms 0.1ms 2.9MB 43ms 0ms crystal 1.7.2
codon 1.py 197ms 0.8ms 5.3MB 187ms 0ms codon 0.15.4

nsieve

Input: 12

lang code time stddev peak-mem mem time(user) time(sys) compiler compiler/runtime
crystal 2.cr 462ms 0.6ms 7.8MB 450ms 0ms crystal 1.7.2
crystal 1.cr 780ms 7.6ms 42.0MB 760ms 0ms crystal 1.7.2
codon 1.py 873ms 79ms 48.3MB 850ms 3ms codon 0.15.4
codon 2.py 1003ms 24ms 106.7MB 977ms 13ms codon 0.15.4

Input: 10

lang code time stddev peak-mem mem time(user) time(sys) compiler compiler/runtime
crystal 2.cr 105ms 0.1ms 4.1MB 97ms 0ms crystal 1.7.2
crystal 1.cr 133ms 0.7ms 12.9MB 120ms 0ms crystal 1.7.2
codon 1.py 150ms 0.2ms 15.1MB 133ms 3ms codon 0.15.4
codon 2.py 185ms 3.8ms 23.9MB 173ms 3ms codon 0.15.4