Programming Language and compiler
Benchmarks

Acton VS Go benchmarks

Current benchmark data was generated on Fri Dec 09 2022, full log can be found HERE

CONTRIBUTIONS are WELCOME!

[x86_64][2 cores] Intel(R) Xeon(R) Platinum 8272CL CPU @ 2.60GHz (Model 85)

* -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
go 1.go 163ms 2.1ms 10.3MB 143ms 3ms go 1.19.4
acton 1.act 548ms 11ms 7.4MB 487ms 43ms actonc 0.14.2

Input: 100000

lang code time stddev peak-mem mem time(user) time(sys) compiler compiler/runtime
go 1.go 50ms 1.1ms 8.4MB 37ms 0ms go 1.19.4
acton 1.act 202ms 1.2ms 5.3MB 183ms 3ms actonc 0.14.2

helloworld

Input: QwQ

lang code time stddev peak-mem mem time(user) time(sys) compiler compiler/runtime
go 1.go 2.0ms 1.5ms 0.0MB 0ms 0ms tinygo 0.25.0
go 1.go 2.6ms 0.3ms 2.9MB 0ms 0ms go 1.19.4
acton 1.act 5.2ms 3.9ms 3.1MB 0ms 0ms actonc 0.14.2

pidigits

Input: 8000

lang code time stddev peak-mem mem time(user) time(sys) compiler compiler/runtime
go 8.go 1330ms 1.6ms 8.5MB 1310ms 7ms go 1.19.4
acton 1.act 4902ms 85ms 7.8MB 4477ms 777ms actonc 0.14.2

Input: 4000

lang code time stddev peak-mem mem time(user) time(sys) compiler compiler/runtime
go 8.go 321ms 3.1ms 8.4MB 303ms 0ms go 1.19.4
acton 1.act 1475ms 7.3ms 6.4MB 1327ms 277ms actonc 0.14.2