YJIT Benchmarks

Details for Benchmarks at 2021-12-08 07:10:43

Overall YJIT is 32.1% faster than interpreted CRuby!
On Railsbench specifically, YJIT is 33.2% 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 190 20 190 75 190 20 190
hexapdf 5 15 20 15 20 15
liquid-render 5 173 20 173 75 173 20 173
mail 5 140 20 140 75 140 20 140
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 596 20 596 75 596 20 596
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 344 20 344 75 344 20 344
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 44 26 20 26
cfunc_itself 5 513 20 513 75 513 20 513
fib 5 384 20 384 75 384 20 384
getivar 5 562 20 562 75 562 20 562
keyword_args 5 430 20 430 75 430 20 430
respond_to 5 131 20 131 75 131 20 131
setivar 5 510 20 510 75 510 20 510

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) 990762 757448 185 1194 0 0% 0 0 0
hexapdf (click) 1096234 893382 596 7998 616 7% 0 0 321
liquid-render (click) 492869 389534 143 1436 95 6% 0 0 1
mail (click) 870826 650646 325 5192 124 2% 0 0 39
psych-load (click) 312225 246666 57 429 1 0% 0 0 0
railsbench (click) 2517538 1907818 1295 9276 263 2% 0 0 26
binarytrees (click) 165171 127877 9 49 0 0% 0 0 0
erubi (click) 291105 229567 8 35 0 0% 0 0 0
erubi_rails (click) 2451170 1769399 260 1982 17 0% 0 0 3
fannkuchredux (click) 180787 139671 6 203 0 0% 0 0 0
jekyll (click) 1878890 1512142 336 3784 185 4% 0 0 0
lee (click) 350506 276736 44 562 67 11% 0 0 12
nbody (click) 174579 135038 8 149 0 0% 0 0 0
optcarrot (click) 503027 440358 196 3567 20 0% 0 0 0
rubykon (click) 306483 247977 138 1530 1 0% 0 0 0
30k_ifelse (click) 5553907 4347985 9261 57795 0 0% 0 0 0
30k_methods (click) 2179891 1660817 5780 19418 0 0% 0 0 0
cfunc_itself (click) 163763 126466 6 40 0 0% 0 0 0
fib (click) 161843 125898 6 29 0 0% 0 0 0
getivar (click) 163955 128625 6 56 0 0% 0 0 0
keyword_args (click) 164595 127147 7 42 0 0% 0 0 0
respond_to (click) 165299 127591 6 55 0 0% 0 0 0
setivar (click) 163891 127149 6 29 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.