YJIT Benchmarks

Details for Benchmarks at 2021-11-13 19:09:43

Overall YJIT is 28.8% faster than interpreted CRuby!
On Railsbench specifically, YJIT is 20.6% 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 YJIT warmups YJIT iters
activerecord 10 126 10 116 10 182
hexapdf 10 10 10 10 10 10
liquid-render 10 105 10 111 10 161
mail 10 115 10 123 10 130
psych-load 10 10 10 10 10 10
railsbench 10 10 10 10 10 10
binarytrees 10 45 10 75 10 62
fannkuchredux 10 10 10 10 10 10
jekyll 10 10 10 10 10 10
lee 10 10 10 12 10 16
nbody 10 171 10 316 10 257
optcarrot 10 10 10 10 10 10
rubykon 10 10 10 10 10 10
30k_ifelse 10 10 10 10 10 54
30k_methods 10 10 10 10 10 17
cfunc_itself 10 202 10 326 10 492
fib 10 94 10 319 10 375
getivar 10 219 10 212 10 540
keyword_args 10 77 10 98 10 415
respond_to 10 78 10 97 10 120
setivar 10 294 10 284 10 462

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) 970026 678871 184 1171 0 0% 0 0 0
hexapdf (click) 1082986 809732 596 8014 614 7% 0 0 320
liquid-render (click) 466999 341097 143 1417 95 6% 0 0 1
mail (click) 852138 586529 339 5202 124 2% 0 0 39
psych-load (click) 296545 211258 57 423 1 0% 0 0 0
railsbench (click) 2586914 1798090 1295 9682 263 2% 0 0 26
binarytrees (click) 113317 80608 9 48 0 0% 0 0 0
fannkuchredux (click) 129317 92618 6 202 0 0% 0 0 0
jekyll (click) 1886954 1392848 336 3945 180 4% 0 0 0
lee (click) 344490 239333 44 566 70 12% 0 0 12
nbody (click) 122725 87443 8 148 0 0% 0 0 0
optcarrot (click) 451685 381143 196 3566 20 0% 0 0 0
rubykon (click) 254629 196677 138 1523 1 0% 0 0 0
30k_ifelse (click) 5502501 4300932 9261 57794 0 0% 0 0 0
30k_methods (click) 2117605 1609394 5780 19351 0 0% 0 0 0
cfunc_itself (click) 111525 79021 6 39 0 0% 0 0 0
fib (click) 110373 78845 6 28 0 0% 0 0 0
getivar (click) 112037 81356 6 55 0 0% 0 0 0
keyword_args (click) 112741 79878 7 41 0 0% 0 0 0
respond_to (click) 114021 80571 6 54 0 0% 0 0 0
setivar (click) 112037 79880 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.