Programming Language and compiler
Benchmarks

Codon VS Acton benchmarks

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

helloworld

Input: QwQ

lang code time stddev peak-mem mem time(user) time(sys) compiler compiler/runtime
acton 1.act 3.8ms 0.3ms 3.9MB 0ms 0ms actonc 0.25.0
codon 1-m.py 11ms 0.6ms 9.0MB 20ms 0ms codon 0.18.2

nbody

Input: 5000000

lang code time stddev peak-mem mem time(user) time(sys) compiler compiler/runtime
codon 1.py 1317ms 2.2ms 8.9MB 1623ms 0ms codon 0.18.2

Input: 500000

lang code time stddev peak-mem mem time(user) time(sys) compiler compiler/runtime
codon 1-m.py 174ms 3.5ms 8.8MB 483ms 0ms codon 0.18.2

nsieve

Input: 12

lang code time stddev peak-mem mem time(user) time(sys) compiler compiler/runtime
codon 1-m.py 444ms 7.4ms 47.7MB 747ms 0ms codon 0.18.2
codon 2.py 1528ms 20ms 100.8MB 1827ms 30ms codon 0.18.2
acton 1.act timeout 0.0ms 561.0MB 6610ms 93ms actonc 0.25.0

Input: 10

lang code time stddev peak-mem mem time(user) time(sys) compiler compiler/runtime
codon 1-m.py 127ms 3.2ms 18.4MB 427ms 0ms codon 0.18.2
codon 2-m.py 398ms 9.8ms 27.1MB 707ms 3ms codon 0.18.2
acton 1.act 2441ms 6.0ms 192.4MB 2940ms 60ms actonc 0.25.0