Programming Language and compiler
Benchmarks

Acton VS D 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
acton 1.act 753ms 14ms 10.1MB 733ms 17ms actonc 0.16.0
d 1.d 3810ms 0.7ms 7.9MB 3800ms 0ms ldc2 1.32.2
d 1.d 4427ms 5.5ms 9.7MB 4410ms 0ms dmd 2.104.1

Input: 100000

lang code time stddev peak-mem mem time(user) time(sys) compiler compiler/runtime
acton 1.act 227ms 6.0ms 11.0MB 210ms 10ms actonc 0.16.0
d 1.d 650ms 0.6ms 6.9MB 640ms 0ms ldc2 1.32.2
d 1.d 799ms 0.5ms 9.7MB 783ms 3ms dmd 2.104.1

helloworld

Input: QwQ

lang code time stddev peak-mem mem time(user) time(sys) compiler compiler/runtime
d 1.d 2.1ms 0.6ms 3.0MB 0ms 0ms ldc2 1.32.2
d 1.d 2.7ms 0.7ms 4.8MB 0ms 0ms dmd 2.104.1
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
d 1.d 3471ms 19ms 7.9MB 3450ms 17ms ldc2 1.32.2
acton 1.act timeout 0.0ms 12.2MB 5747ms 627ms actonc 0.16.0
d 1.d timeout 0.0ms 9.9MB 4983ms 7ms dmd 2.104.1

Input: 4000

lang code time stddev peak-mem mem time(user) time(sys) compiler compiler/runtime
d 1.d 827ms 1.5ms 7.9MB 813ms 3ms ldc2 1.32.2
d 1.d 1739ms 3.6ms 9.9MB 1727ms 0ms dmd 2.104.1
acton 1.act 2512ms 118ms 8.3MB 2777ms 297ms actonc 0.16.0