YJIT Benchmarks

Details for Benchmarks at 2021-11-17 07:10:30

Overall YJIT is 29.9% faster than interpreted CRuby!
On Railsbench specifically, YJIT is 23.0% 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 125 10 115 10 176
hexapdf 10 10 10 10 10 10
liquid-render 10 104 10 115 10 164
mail 10 117 10 124 10 131
psych-load 10 10 10 10 10 10
railsbench 10 10 10 10 10 10
binarytrees 10 46 10 78 10 63
fannkuchredux 10 10 10 10 10 10
jekyll 10 10 10 10 10 10
lee 10 10 10 12 10 15
nbody 10 165 10 316 10 262
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 197 10 317 10 504
fib 10 89 10 319 10 374
getivar 10 203 10 212 10 541
keyword_args 10 78 10 96 10 431
respond_to 10 79 10 94 10 118
setivar 10 298 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) 968618 678292 184 1167 0 0% 0 0 0
hexapdf (click) 1081258 808305 596 8005 616 7% 0 0 320
liquid-render (click) 466935 340733 143 1417 95 6% 0 0 1
mail (click) 850858 585734 339 5198 124 2% 0 0 39
psych-load (click) 296993 211301 57 436 1 0% 0 0 0
railsbench (click) 2587618 1797672 1295 9679 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) 1880874 1387909 336 3892 179 4% 0 0 0
lee (click) 344618 239446 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) 254181 196380 138 1514 1 0% 0 0 0
30k_ifelse (click) 5501925 4300583 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) 109797 78496 6 28 0 0% 0 0 0
getivar (click) 111525 81007 6 55 0 0% 0 0 0
keyword_args (click) 112165 79529 7 41 0 0% 0 0 0
respond_to (click) 114341 80899 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.