YJIT Benchmarks

Details for Benchmarks at 2021-11-06 07:10:11

Overall YJIT is 30.4% faster than interpreted CRuby!
On Railsbench specifically, YJIT is 23.8% 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 123 10 115 10 175
hexapdf 10 10 10 10 10 10
liquid-render 10 103 10 111 10 164
mail 10 111 10 119 10 127
psych-load 10 10 10 10 10 10
railsbench 10 10 10 10 10 10
binarytrees 10 49 10 70 10 62
fannkuchredux 10 10 10 10 10 10
jekyll 10 10 10 10 10 10
lee 10 10 10 14 10 15
nbody 10 174 10 331 10 265
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 215 10 334 10 508
fib 10 95 10 307 10 375
getivar 10 229 10 211 10 542
keyword_args 10 72 10 98 10 430
respond_to 10 80 10 89 10 118
setivar 10 298 10 265 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) 971178 679716 184 1180 0 0% 0 0 0
hexapdf (click) 1089130 814135 604 8097 649 8% 0 0 320
liquid-render (click) 468087 341505 143 1420 96 6% 0 0 1
mail (click) 835498 574368 339 5032 124 2% 0 0 39
psych-load (click) 294497 209735 57 423 1 0% 0 0 0
railsbench (click) 2573410 1789566 1295 9562 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) 1889322 1394570 336 3964 179 4% 0 0 0
lee (click) 345130 239770 44 566 70 12% 0 0 12
nbody (click) 122149 87094 8 148 0 0% 0 0 0
optcarrot (click) 451109 380794 196 3566 20 0% 0 0 0
rubykon (click) 256933 198686 138 1554 2 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) 111333 78888 6 39 0 0% 0 0 0
fib (click) 110373 78845 6 28 0 0% 0 0 0
getivar (click) 112101 81356 6 55 0 0% 0 0 0
keyword_args (click) 113061 80206 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.