Programming Language and compiler
Benchmarks

Acton VS Crystal benchmarks

Current benchmark data was generated on Thu Jul 13 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.)

edigits

Input: 250001

lang code time stddev peak-mem mem time(user) time(sys) compiler compiler/runtime
crystal 1.cr 80ms 0.7ms 7.2MB 63ms 7ms crystal 1.9.0
acton 1.act 753ms 14ms 10.1MB 733ms 17ms actonc 0.16.0

Input: 100000

lang code time stddev peak-mem mem time(user) time(sys) compiler compiler/runtime
crystal 1.cr 29ms 0.7ms 5.4MB 17ms 3ms crystal 1.9.0
acton 1.act 227ms 6.0ms 11.0MB 210ms 10ms actonc 0.16.0

helloworld

Input: QwQ

lang code time stddev peak-mem mem time(user) time(sys) compiler compiler/runtime
crystal 1.cr 2.3ms 0.5ms 3.0MB 0ms 0ms crystal 1.9.0
acton 1.act 8.6ms 2.5ms 4.3MB 0ms 0ms actonc 0.16.0

pidigits

Input: 8000

lang code time stddev peak-mem mem time(user) time(sys) compiler compiler/runtime
crystal 1.cr 2576ms 68ms 6.6MB 2557ms 3ms crystal 1.9.0
acton 1.act timeout 0.0ms 12.2MB 5747ms 627ms actonc 0.16.0

Input: 4000

lang code time stddev peak-mem mem time(user) time(sys) compiler compiler/runtime
crystal 1.cr 583ms 11ms 5.4MB 570ms 0ms crystal 1.9.0
acton 1.act 2512ms 118ms 8.3MB 2777ms 297ms actonc 0.16.0