Codon VS Wasm benchmarks

Current benchmark data was generated on Mon May 19 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
wasm 1.rs 6.8ms 0.2ms 18.0MB 0ms 0ms wasmtime 32.0.0
codon 1-m.py 12ms 0.7ms 8.8MB 20ms 0ms codon 0.18.2

nbody

Input: 5000000

lang code time stddev peak-mem mem time(user) time(sys) compiler compiler/runtime
wasm 1.rs 407ms 0.1ms 18.2MB 393ms 0ms wasmtime 32.0.0
wasm 2.rs 563ms 1.8ms 17.8MB 550ms 0ms wasmtime 32.0.0
codon 1.py 1323ms 14ms 8.9MB 1630ms 0ms codon 0.18.2

Input: 500000

lang code time stddev peak-mem mem time(user) time(sys) compiler compiler/runtime
wasm 1.rs 49ms 0.9ms 18.0MB 40ms 0ms wasmtime 32.0.0
wasm 2.rs 65ms 1.2ms 18.1MB 53ms 0ms wasmtime 32.0.0
codon 1-m.py 177ms 3.9ms 8.8MB 487ms 0ms codon 0.18.2

nsieve

Input: 12

lang code time stddev peak-mem mem time(user) time(sys) compiler compiler/runtime
wasm 2.rs 368ms 9.3ms 22.8MB 357ms 0ms wasmtime 32.0.0
codon 1-m.py 455ms 9.2ms 47.7MB 757ms 0ms codon 0.18.2
wasm 1.rs 476ms 1.3ms 56.7MB 460ms 0ms wasmtime 32.0.0
codon 2.py 1561ms 6.3ms 100.8MB 1870ms 23ms codon 0.18.2

Input: 10

lang code time stddev peak-mem mem time(user) time(sys) compiler compiler/runtime
wasm 1.rs 96ms 3.0ms 27.5MB 83ms 0ms wasmtime 32.0.0
wasm 2.rs 97ms 2.1ms 18.9MB 83ms 0ms wasmtime 32.0.0
codon 1-m.py 126ms 3.4ms 18.4MB 433ms 0ms codon 0.18.2
codon 2-m.py 398ms 2.8ms 27.2MB 707ms 10ms codon 0.18.2