Programming Language and compiler
Benchmarks

Acton VS Haxe benchmarks

Current benchmark data was generated on Sat Nov 16 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
acton 1.act 263ms 9.9ms 7.1MB 227ms 70ms actonc 0.24.1

Input: 100000

lang code time stddev peak-mem mem time(user) time(sys) compiler compiler/runtime
acton 1.act 95ms 8.4ms 5.5MB 70ms 30ms actonc 0.24.1

helloworld

Input: QwQ

lang code time stddev peak-mem mem time(user) time(sys) compiler compiler/runtime
haxe 1.hx 2.2ms 0.3ms 4.7MB 0ms 0ms haxe/hl/c 4.3.6
haxe 1.hx 2.6ms 0.1ms 4.4MB 0ms 0ms haxe/cpp 4.3.6
haxe 1.hx 3.7ms 0.3ms 5.3MB 0ms 0ms haxe/hl/jit 1.14.0
acton 1.act 4.3ms 0.4ms 8.0MB 0ms 0ms actonc 0.24.1

pidigits

Input: 8000

lang code time stddev peak-mem mem time(user) time(sys) compiler compiler/runtime
acton 1-m.act 3110ms 78ms 6.7MB 2773ms 2133ms actonc 0.24.1

Input: 4000

lang code time stddev peak-mem mem time(user) time(sys) compiler compiler/runtime
acton 1-m.act 932ms 61ms 5.7MB 810ms 600ms actonc 0.24.1