YJIT Benchmarks

Details for Benchmarks at 2021-12-02 19:10:23

Overall YJIT is 28.5% faster than interpreted CRuby!
On Railsbench specifically, YJIT is 17.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 MJIT warmups MJIT iters YJIT warmups YJIT iters
activerecord 5 182 20 182 75 182 20 182
hexapdf 5 15 20 15 20 15
liquid-render 5 172 20 172 75 172 20 172
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 85 20 85 75 85 20 85
erubi 5 49 20 49 75 49 20 49
erubi_rails 5 564 20 564 75 564 20 564
fannkuchredux 5 15 20 15 51 15 20 15
jekyll 5 15 20 15 35 15 20 15
lee 5 27 20 27 75 27 20 27
nbody 5 343 20 343 75 343 20 343
optcarrot 5 15 20 15 75 15 20 15
rubykon 5 15 20 15 43 15 20 15
30k_ifelse 5 65 20 65 65 65 20 65
30k_methods 5 26 20 26 43 26 20 26
cfunc_itself 5 519 20 519 75 519 20 519
fib 5 384 20 384 75 384 20 384
getivar 5 562 20 562 75 562 20 562
keyword_args 5 429 20 429 75 429 20 429
respond_to 5 130 20 130 75 130 20 130
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) 989610 745393 185 1194 0 0% 0 0 0
hexapdf (click) 1095658 873798 596 7998 614 7% 0 0 321
liquid-render (click) 493445 383216 143 1458 95 6% 0 0 1
mail (click) 875818 647125 325 5251 124 2% 0 0 39
psych-load (click) 312161 242887 57 436 1 0% 0 0 0
railsbench (click) 2590690 1934911 1293 9695 263 2% 0 0 26
binarytrees (click) 163699 125398 9 49 0 0% 0 0 0
erubi (click) 290145 225982 8 35 0 0% 0 0 0
erubi_rails (click) 2452450 1755251 260 1987 17 0% 0 0 3
fannkuchredux (click) 179699 137408 6 203 0 0% 0 0 0
jekyll (click) 1902122 1512042 336 3940 179 4% 0 0 0
lee (click) 349418 272343 44 562 67 11% 0 0 12
nbody (click) 173107 132369 8 149 0 0% 0 0 0
optcarrot (click) 501555 431559 196 3567 20 0% 0 0 0
rubykon (click) 307123 245362 138 1546 1 0% 0 0 0
30k_ifelse (click) 5552499 4345506 9261 57795 0 0% 0 0 0
30k_methods (click) 2167411 1653835 5780 19352 0 0% 0 0 0
cfunc_itself (click) 161907 123811 6 40 0 0% 0 0 0
fib (click) 160179 123286 6 29 0 0% 0 0 0
getivar (click) 162483 126146 6 56 0 0% 0 0 0
keyword_args (click) 163123 124668 7 42 0 0% 0 0 0
respond_to (click) 164403 125481 6 55 0 0% 0 0 0
setivar (click) 161843 124321 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.