YJIT Benchmarks

Details for Benchmarks at 2021-10-28 19:10:36

Overall YJIT is 27.6% faster than interpreted CRuby!
On Railsbench specifically, YJIT is 21.9% 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 129 10 119 10 171
hexapdf 10 10 10 10 10 10
liquid-render 10 105 10 110 10 148
mail 10 117 10 121 10 130
psych-load 10 10 10 10 10 10
railsbench 10 10 10 10 10 10
binarytrees 10 43 10 69 10 56
fannkuchredux 10 10 10 10 10 10
jekyll 10 10 10 10 10 10
lee 10 10 10 13 10 16
nbody 10 174 10 325 10 256
optcarrot 10 10 10 10 10 10
rubykon 10 10 10 10 10 10
30k_ifelse 10 10 10 10 10 53
30k_methods 10 10 10 10 10 17
cfunc_itself 10 207 10 339 10 477
fib 10 92 10 307 10 375
getivar 10 207 10 211 10 529
keyword_args 10 75 10 97 10 431
respond_to 10 73 10 88 10 112
setivar 10 284 10 265 10 459

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) 1115546 869951 185 1147 0 0% 0 0 0
hexapdf (click) 1073396 897879 603 7827 619 7% 0 0 320
liquid-render (click) 457985 374772 143 1249 95 7% 0 0 1
mail (click) 832564 645002 339 5006 124 2% 0 0 39
psych-load (click) 192298 155738 56 409 1 0% 0 0 0
railsbench (click) 2587761 2020879 1293 9606 262 2% 0 0 26
binarytrees (click) 114474 90633 9 48 0 0% 0 0 0
fannkuchredux (click) 130794 104636 6 202 0 0% 0 0 0
jekyll (click) 1960794 1630455 336 3744 173 4% 0 0 0
lee (click) 235114 181569 85 1082 114 10% 1 0 13
nbody (click) 123818 98495 8 148 0 0% 0 0 0
optcarrot (click) 460714 430911 196 3566 20 0% 0 0 0
rubykon (click) 255914 220973 139 1500 2 0% 0 0 0
30k_ifelse (click) 5562090 4891562 9261 57794 0 0% 0 0 0
30k_methods (click) 2118634 1817379 5780 19351 0 0% 0 0 0
cfunc_itself (click) 112682 89056 6 39 0 0% 0 0 0
fib (click) 110826 88251 6 28 0 0% 0 0 0
getivar (click) 112618 91092 6 55 0 0% 0 0 0
keyword_args (click) 113194 89434 7 41 0 0% 0 0 0
respond_to (click) 115562 90994 6 54 0 0% 0 0 0
setivar (click) 113194 89795 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.