Programming Language and compiler
Benchmarks

Codon VS Typescript benchmarks

Current benchmark data was generated on Tue Mar 25 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
codon 1-m.py 11ms 0.7ms 8.6MB 20ms 0ms codon 0.18.2
typescript 1.ts 28ms 0.8ms 45.9MB 10ms 8ms deno 2.2.5

nbody

Input: 5000000

lang code time stddev peak-mem mem time(user) time(sys) compiler compiler/runtime
typescript 6.ts 466ms 0.7ms 56.6MB 450ms 10ms deno 2.2.5
codon 1.py 1322ms 1.2ms 8.8MB 1630ms 0ms codon 0.18.2

Input: 500000

lang code time stddev peak-mem mem time(user) time(sys) compiler compiler/runtime
typescript 6.ts 80ms 3.2ms 54.6MB 63ms 10ms deno 2.2.5
codon 1-m.py 176ms 3.4ms 9.0MB 487ms 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 461ms 8.3ms 47.7MB 763ms 0ms codon 0.18.2
codon 2.py 1572ms 19ms 100.8MB 1877ms 27ms codon 0.18.2

Input: 10

lang code time stddev peak-mem mem time(user) time(sys) compiler compiler/runtime
codon 1-m.py 125ms 0.2ms 18.6MB 430ms 0ms codon 0.18.2
codon 2-m.py 397ms 1.3ms 27.1MB 707ms 3ms codon 0.18.2