YJIT Benchmarks

Details for Benchmarks at 2021-12-17 19:10:43

Overall YJIT is 30.0% faster than interpreted CRuby!
On Railsbench specifically, YJIT is 32.3% 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 173 20 173 75 173 20 173
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 88 20 88 75 88 20 88
erubi 5 52 20 52 75 52 20 52
erubi_rails 5 604 20 604 75 604 20 604
fannkuchredux 5 15 20 15 50 15 20 15
jekyll 5 15 20 15 36 15 20 15
lee 5 27 20 27 75 27 20 27
nbody 5 344 20 344 75 344 20 344
optcarrot 5 15 20 15 75 15 20 15
rubykon 5 15 20 15 43 15 20 15
30k_ifelse 5 64 20 64 75 64 20 64
30k_methods 5 26 20 26 40 26 20 26
cfunc_itself 5 507 20 507 75 507 20 507
fib 5 383 20 383 75 383 20 383
getivar 5 563 20 563 75 563 20 563
keyword_args 5 435 20 435 75 435 20 435
respond_to 5 129 20 129 75 129 20 129
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) 971690 740620 185 1194 0 0% 0 0 0
hexapdf (click) 1077162 876984 596 7997 613 7% 0 0 321
liquid-render (click) 468151 369968 143 1435 95 6% 0 0 1
mail (click) 872938 648978 325 5424 124 2% 0 0 39
psych-load (click) 291233 228830 57 423 1 0% 0 0 0
railsbench (click) 2495714 1885727 1295 9242 263 2% 0 0 26
binarytrees (click) 112805 86408 9 48 0 0% 0 0 0
erubi (click) 270817 212350 8 35 0 0% 0 0 0
erubi_rails (click) 2440802 1757275 260 1950 17 0% 0 0 3
fannkuchredux (click) 128805 98418 6 202 0 0% 0 0 0
jekyll (click) 1858922 1495210 336 3749 186 4% 0 0 0
lee (click) 329441 258658 43 557 66 11% 0 0 12
nbody (click) 122213 93609 8 148 0 0% 0 0 0
optcarrot (click) 451045 399145 196 3566 20 0% 0 0 0
rubykon (click) 253669 206018 138 1517 1 0% 0 0 0
30k_ifelse (click) 5502501 4307061 9261 57794 0 0% 0 0 0
30k_methods (click) 2117093 1615194 5780 19351 0 0% 0 0 0
cfunc_itself (click) 111397 85037 6 39 0 0% 0 0 0
fib (click) 109925 84645 6 28 0 0% 0 0 0
getivar (click) 111589 87156 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) 111525 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.