Acton VS Chapel benchmarks

Current benchmark data was generated on Thu Feb 01 2024, 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.)

edigits

Input: 250001

lang code time stddev peak-mem mem time(user) time(sys) compiler compiler/runtime
chapel 1.chpl 79ms 0.6ms 36.5MB 70ms 0ms chpl 1.31.0
acton 1.act 518ms 8.0ms 12.4MB 543ms 47ms actonc 0.19.2

Input: 100000

lang code time stddev peak-mem mem time(user) time(sys) compiler compiler/runtime
chapel 1.chpl 40ms 0.2ms 34.5MB 30ms 0ms chpl 1.31.0
acton 1.act 167ms 8.8ms 10.8MB 153ms 30ms actonc 0.19.2

helloworld

Input: QwQ

lang code time stddev peak-mem mem time(user) time(sys) compiler compiler/runtime
acton 1.act 4.2ms 0.4ms 6.4MB 0ms 0ms actonc 0.19.2
chapel 1.chpl 16ms 0.2ms 32.8MB 10ms 0ms chpl 1.31.0

pidigits

Input: 8000

lang code time stddev peak-mem mem time(user) time(sys) compiler compiler/runtime
chapel 2.chpl 452ms 1.3ms 34.4MB 443ms 0ms chpl 1.31.0
acton 1.act timeout 0.0ms 10.8MB 7663ms 1610ms actonc 0.19.2

Input: 4000

lang code time stddev peak-mem mem time(user) time(sys) compiler compiler/runtime
chapel 2.chpl 122ms 1.3ms 34.2MB 113ms 0ms chpl 1.31.0
acton 1-m.act 1681ms 170ms 10.7MB 2257ms 673ms actonc 0.19.2