YJIT Benchmarks

Details for Benchmarks at 2021-12-25 13:35:55

Overall YJIT is 27.1% faster than interpreted CRuby!
On Railsbench specifically, YJIT is 22.9% 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 186 20 186 75 186 20 186
hexapdf 5 15 20 15 20 15
liquid-render 5 153 20 153 75 153 20 153
mail 5 136 20 136 75 136 20 136
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 51 20 51 75 51 20 51
erubi_rails 5 585 20 585 75 585 20 585
fannkuchredux 5 15 20 15 54 15 20 15
jekyll 5 15 20 15 36 15 20 15
lee 5 26 20 26 75 26 20 26
nbody 5 341 20 341 75 341 20 341
optcarrot 5 15 20 15 75 15 20 15
rubykon 5 15 20 15 44 15 20 15
30k_ifelse 5 65 20 65 75 65 20 65
30k_methods 5 26 20 26 42 26 20 26
cfunc_itself 5 505 20 505 75 505 20 505
fib 5 384 20 384 75 384 20 384
getivar 5 564 20 564 75 564 20 564
keyword_args 5 436 20 436 75 436 20 436
respond_to 5 122 20 122 75 122 20 122
setivar 5 436 20 436 75 436 20 436

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) 976234 744991 185 1182 0 0% 0 0 0
hexapdf (click) 1122346 916856 599 8110 620 7% 0 0 321
liquid-render (click) 472695 373627 143 1441 96 6% 0 0 1
mail (click) 832490 619352 325 5047 124 2% 0 0 39
psych-load (click) 299041 235617 57 423 1 0% 0 0 0
railsbench (click) 2519010 1904332 1295 9304 266 2% 0 0 26
binarytrees (click) 112933 86584 9 48 0 0% 0 0 0
erubi (click) 278625 219180 8 35 0 0% 0 0 0
erubi_rails (click) 2462114 1774277 260 1983 17 0% 0 0 3
fannkuchredux (click) 129061 98707 6 202 0 0% 0 0 0
jekyll (click) 1850090 1486706 338 3786 185 4% 0 0 0
lee (click) 336993 265350 43 557 70 12% 0 0 12
nbody (click) 122469 93898 8 148 0 0% 0 0 0
optcarrot (click) 451557 399597 196 3566 20 0% 0 0 0
rubykon (click) 253797 206345 138 1519 2 0% 0 0 0
30k_ifelse (click) 5502565 4307237 9261 57794 0 0% 0 0 0
30k_methods (click) 2117669 1615647 5780 19351 0 0% 0 0 0
cfunc_itself (click) 111653 85326 6 39 0 0% 0 0 0
fib (click) 109989 84821 6 28 0 0% 0 0 0
getivar (click) 111845 87445 6 55 0 0% 0 0 0
keyword_args (click) 112485 85967 7 41 0 0% 0 0 0
respond_to (click) 113637 86667 6 54 0 0% 0 0 0
setivar (click) 111781 85969 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.