YJIT Benchmarks

Details for Benchmarks at 2022-01-20 19:11:59 GMT

YJIT metrics from the yjit-bench suite

Overall YJIT is 30.6% faster than interpreted CRuby!
On Railsbench specifically, YJIT is 30.3% faster than CRuby!

Performance on Headline Benchmarks

Speed of each Ruby implementation relative to the baseline CRuby measurement. Higher is better.

Memory Usage on Headline Benchmarks

Memory usage of each Ruby implementation relative to the baseline CRuby measurement. Lower is better.

Performance on Other Benchmarks

Speed of each Ruby implementation relative to the baseline CRuby measurement. Higher is better.

Memory Usage on Other Benchmarks

Memory usage of each Ruby implementation relative to the baseline CRuby measurement. Lower is better.

Performance on MicroBenchmarks

Speed of each Ruby implementation relative to the baseline CRuby measurement. Higher is better.

Memory Usage on MicroBenchmarks

Memory usage of each Ruby implementation relative to the baseline CRuby measurement. Lower is better.

Want Raw Graphs and CSV?

Benchmarks Speed Details

Benchmark Memory Usage Details

Number of Iterations and Warmups Tested

bench No JIT warmups No JIT iters MJIT3.0 warmups MJIT3.0 iters MJIT warmups MJIT iters YJIT warmups YJIT iters
activerecord 5 187 20 187 75 187 20 187
hexapdf 5 15 20 15 20 15
liquid-render 5 181 20 181 75 181 20 181
mail 5 142 20 142 75 142 20 142
psych-load 5 15 20 15 75 15 20 15
railsbench 5 15 20 15 75 15 20 15
binarytrees 5 85 20 85 75 85 20 85
erubi 5 55 20 55 75 55 20 55
erubi_rails 5 1017 20 1017 75 1017 20 1017
fannkuchredux 5 15 20 15 75 15 20 15
lee 5 26 20 26 75 26 20 26
nbody 5 344 20 344 75 344 20 344
optcarrot 5 15 20 15 75 15 20 15
rubykon 5 15 20 15 44 15 20 15
30k_ifelse 5 65 20 65 69 65 20 65
30k_methods 5 26 20 26 45 26 20 26
cfunc_itself 5 531 20 531 75 531 20 531
fib 5 384 20 384 75 384 20 384
getivar 5 958 20 958 75 958 20 958
keyword_args 5 453 20 453 75 453 20 453
respond_to 5 119 20 119 75 119 20 119
setivar 5 2207 20 2207 75 2207 20 2207

Different Ruby configurations want different amounts of warmup. With no JIT, CRuby needs hardly any. YJIT and MJIT 3.0 both warm up quite quickly, while MJIT in 3.1 often slows down for a time as it compiles, after an unpredictable delay.

Benchmark YJIT Stats

Hover your cursor over the benchmark names for descriptions of each benchmark.

bench Exit Report Inline Outlined Comp iSeqs Comp Blocks Inval Inval Ratio Bind Alloc Bind Set Const Bumps
activerecord (click) 997137 765285 185 1196 0 0% 0 0 0
hexapdf (click) 1121425 919443 599 8169 613 7% 0 0 321
liquid-render (click) 491473 391012 143 1542 95 6% 0 0 1
mail (click) 910545 682774 325 5529 125 2% 0 0 39
psych-load (click) 330513 261442 59 434 1 0% 0 0 0
railsbench (click) 2538065 1936418 1297 9348 268 2% 0 0 26
binarytrees (click) 151505 115984 11 59 0 0% 0 0 0
erubi (click) 328785 261752 10 79 0 0% 0 0 0
erubi_rails (click) 1918545 1446110 262 1958 18 0% 0 0 3
fannkuchredux (click) 165265 126682 8 189 0 0% 0 0 0
lee (click) 370321 291881 45 587 69 11% 0 0 12
nbody (click) 161233 123514 10 159 0 0% 0 0 0
optcarrot (click) 487953 428815 198 3576 20 0% 0 0 0
rubykon (click) 294033 237157 140 1542 1 0% 0 0 0
30k_ifelse (click) 5540497 4336308 9263 57805 0 0% 0 0 0
30k_methods (click) 2155665 1644770 5782 19362 0 0% 0 0 0
cfunc_itself (click) 149905 114613 8 50 0 0% 0 0 0
fib (click) 148497 114221 8 39 0 0% 0 0 0
getivar (click) 150225 116732 8 66 0 0% 0 0 0
keyword_args (click) 150801 115254 9 52 0 0% 0 0 0
respond_to (click) 152593 116396 8 65 0 0% 0 0 0
setivar (click) 150737 115585 8 39 0 0% 0 0 0

YJIT stats correspond to the YJIT stats exit report.

Note: currently, all stats are collected on x86_64, not ARM.

Raw JSON data files

All graphs and table data in this page comes from processing these data files, which come from benchmark runs.