YJIT Benchmarks

Details for Benchmarks at 2021-11-16 07:10:22

Overall YJIT is 30.0% faster than interpreted CRuby!
On Railsbench specifically, YJIT is 23.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 122 10 112 10 179
hexapdf 10 10 10 10 10 10
liquid-render 10 106 10 114 10 160
mail 10 117 10 125 10 131
psych-load 10 10 10 10 10 10
railsbench 10 10 10 10 10 10
binarytrees 10 46 10 76 10 60
fannkuchredux 10 10 10 10 10 10
jekyll 10 10 10 10 10 10
lee 10 10 10 12 10 15
nbody 10 171 10 315 10 266
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 212 10 326 10 504
fib 10 91 10 321 10 373
getivar 10 196 10 212 10 539
keyword_args 10 75 10 98 10 428
respond_to 10 78 10 96 10 119
setivar 10 287 10 283 10 437

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) 966954 677008 184 1158 0 0% 0 0 0
hexapdf (click) 1081898 809054 595 8009 614 7% 0 0 320
liquid-render (click) 469175 342415 143 1450 95 6% 0 0 1
mail (click) 855018 588192 339 5232 124 2% 0 0 39
psych-load (click) 298145 212106 57 436 1 0% 0 0 0
railsbench (click) 2576546 1790839 1295 9579 263 2% 0 0 26
binarytrees (click) 113317 80608 9 48 0 0% 0 0 0
fannkuchredux (click) 128741 92269 6 202 0 0% 0 0 0
jekyll (click) 1887978 1393226 336 3927 179 4% 0 0 0
lee (click) 344618 239471 44 566 70 12% 0 0 12
nbody (click) 122725 87443 8 148 0 0% 0 0 0
optcarrot (click) 451109 380794 196 3566 20 0% 0 0 0
rubykon (click) 255013 197169 139 1529 1 0% 0 0 0
30k_ifelse (click) 5502501 4300932 9261 57794 0 0% 0 0 0
30k_methods (click) 2117029 1609045 5780 19351 0 0% 0 0 0
cfunc_itself (click) 111333 78888 6 39 0 0% 0 0 0
fib (click) 109797 78496 6 28 0 0% 0 0 0
getivar (click) 112101 81356 6 55 0 0% 0 0 0
keyword_args (click) 112165 79529 7 41 0 0% 0 0 0
respond_to (click) 113445 80222 6 54 0 0% 0 0 0
setivar (click) 111461 79531 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.