YJIT Benchmarks

Details for Benchmarks at 2021-12-16 07:10:55

Overall YJIT is 30.0% faster than interpreted CRuby!
On Railsbench specifically, YJIT is 24.7% faster than CRuby!

The basic "faster" measurement is the geomean of all "headlining" x86 benchmarks on this page.

Headlining Benchmarks

These are "headlining" because the "overall" speedup above is based on these benchmarks specifically.

Speed of each Ruby implementation (iterations/second) relative to the CRuby interpreter. Higher is better.

Other Benchmarks

Speed of each Ruby implementation (iterations/second) relative to the CRuby interpreter. Higher is better.

MicroBenchmarks

Speed of each Ruby implementation (iterations/second) relative to the CRuby interpreter. Higher 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 189 20 189 75 189 20 189
hexapdf 5 15 20 15 20 15
liquid-render 5 174 20 174 75 174 20 174
mail 5 139 20 139 75 139 20 139
psych-load 5 15 20 15 75 15 20 15
railsbench 5 15 20 15 75 15 20 15
binarytrees 5 87 20 87 75 87 20 87
erubi 5 51 20 51 75 51 20 51
erubi_rails 5 588 20 588 75 588 20 588
fannkuchredux 5 15 20 15 50 15 20 15
jekyll 5 15 20 15 36 15 20 15
lee 5 26 20 26 75 26 20 26
nbody 5 343 20 343 75 343 20 343
optcarrot 5 15 20 15 75 15 20 15
rubykon 5 15 20 15 43 15 20 15
30k_ifelse 5 65 20 65 75 65 20 65
30k_methods 5 27 20 27 44 27 20 27
cfunc_itself 5 483 20 483 75 483 20 483
fib 5 382 20 382 75 382 20 382
getivar 5 564 20 564 75 564 20 564
keyword_args 5 437 20 437 75 437 20 437
respond_to 5 128 20 128 75 128 20 128
setivar 5 481 20 481 75 481 20 481

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) 971818 740638 185 1194 0 0% 0 0 0
hexapdf (click) 1076650 876724 595 7996 616 7% 0 0 321
liquid-render (click) 467767 369627 143 1435 95 6% 0 0 1
mail (click) 853226 634980 325 5223 124 2% 0 0 39
psych-load (click) 291745 229159 57 423 1 0% 0 0 0
railsbench (click) 2494626 1885431 1295 9236 263 2% 0 0 26
binarytrees (click) 112997 86521 9 48 0 0% 0 0 0
erubi (click) 270753 212325 8 35 0 0% 0 0 0
erubi_rails (click) 2468066 1777897 261 1994 17 0% 0 0 3
fannkuchredux (click) 128805 98418 6 202 0 0% 0 0 0
jekyll (click) 1857642 1494019 336 3781 186 4% 0 0 0
lee (click) 329889 258987 43 557 66 11% 0 0 12
nbody (click) 122213 93609 8 148 0 0% 0 0 0
optcarrot (click) 451621 399474 196 3566 20 0% 0 0 0
rubykon (click) 255717 207487 138 1531 1 0% 0 0 0
30k_ifelse (click) 5501989 4306732 9261 57794 0 0% 0 0 0
30k_methods (click) 2117285 1615307 5780 19351 0 0% 0 0 0
cfunc_itself (click) 111461 85037 6 39 0 0% 0 0 0
fib (click) 110053 84758 6 28 0 0% 0 0 0
getivar (click) 111781 87269 6 55 0 0% 0 0 0
keyword_args (click) 112229 85678 7 41 0 0% 0 0 0
respond_to (click) 113509 86491 6 54 0 0% 0 0 0
setivar (click) 111589 85680 6 28 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.