Php VS Acton benchmarks

Current benchmark data was generated on Wed Jan 22 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.)

binarytrees

Input: 18

lang code time stddev peak-mem mem time(user) time(sys) compiler compiler/runtime
acton 1.act timeout 0.0ms 69.0MB 5947ms 107ms actonc 0.24.1
php 1.php timeout 0.0ms 141.9MB 4957ms 23ms php 8.2.27

Input: 15

lang code time stddev peak-mem mem time(user) time(sys) compiler compiler/runtime
php 1.php 619ms 7.3ms 62.7MB 590ms 13ms php 8.2.27
acton 1.act 840ms 40ms 12.0MB 967ms 77ms actonc 0.24.1

helloworld

Input: QwQ

lang code time stddev peak-mem mem time(user) time(sys) compiler compiler/runtime
acton 1.act 3.8ms 0.3ms 8.3MB 0ms 0ms actonc 0.24.1
php 1.php 50ms 1.1ms 52.6MB 22ms 12ms php 8.2.27

merkletrees

Input: 17

lang code time stddev peak-mem mem time(user) time(sys) compiler compiler/runtime
acton 1.act 3246ms 7.1ms 101.8MB 3543ms 43ms actonc 0.24.1
php 1.php 3744ms 64ms 113.9MB 3703ms 23ms php 8.2.27

Input: 15

lang code time stddev peak-mem mem time(user) time(sys) compiler compiler/runtime
acton 1.act 691ms 2.3ms 32.5MB 723ms 30ms actonc 0.24.1
php 1.php 826ms 9.2ms 67.1MB 787ms 23ms php 8.2.27