YJIT Benchmarks

Details for Benchmarks at 2021-11-09 19:14:10

Overall YJIT is 31.3% faster than interpreted CRuby!
On Railsbench specifically, YJIT is 24.5% 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 127 10 118 10 183
hexapdf 10 10 10 10 10 10
liquid-render 10 103 10 114 10 166
mail 10 117 10 122 10 131
psych-load 10 10 10 10 10 10
railsbench 10 10 10 10 10 10
binarytrees 10 45 10 69 10 62
fannkuchredux 10 10 10 10 10 10
jekyll 10 10 10 10 10 10
lee 10 10 10 14 10 15
nbody 10 173 10 331 10 264
optcarrot 10 10 10 10 10 10
rubykon 10 10 10 10 10 10
30k_ifelse 10 10 10 10 10 52
30k_methods 10 10 10 10 10 17
cfunc_itself 10 216 10 335 10 500
fib 10 95 10 307 10 375
getivar 10 211 10 214 10 541
keyword_args 10 74 10 97 10 427
respond_to 10 77 10 89 10 119
setivar 10 282 10 258 10 500

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) 970922 679596 184 1180 0 0% 0 0 0
hexapdf (click) 1087658 812691 604 8072 648 8% 0 0 320
liquid-render (click) 470711 343244 143 1440 96 6% 0 0 1
mail (click) 836650 574983 339 5043 124 2% 0 0 39
psych-load (click) 296545 211258 57 423 1 0% 0 0 0
railsbench (click) 2577570 1791606 1295 9582 263 2% 0 0 26
binarytrees (click) 113253 80720 9 48 0 0% 0 0 0
fannkuchredux (click) 129637 92946 6 202 0 0% 0 0 0
jekyll (click) 1888490 1393133 336 3931 179 4% 0 0 0
lee (click) 345130 239795 44 566 70 12% 0 0 12
nbody (click) 122725 87443 8 148 0 0% 0 0 0
optcarrot (click) 451621 381143 196 3566 20 0% 0 0 0
rubykon (click) 254821 196922 138 1528 1 0% 0 0 0
30k_ifelse (click) 5502437 4300932 9261 57794 0 0% 0 0 0
30k_methods (click) 2117541 1609506 5780 19351 0 0% 0 0 0
cfunc_itself (click) 111845 79237 6 39 0 0% 0 0 0
fib (click) 110373 78845 6 28 0 0% 0 0 0
getivar (click) 111525 81007 6 55 0 0% 0 0 0
keyword_args (click) 112677 79990 7 41 0 0% 0 0 0
respond_to (click) 114341 80899 6 54 0 0% 0 0 0
setivar (click) 111973 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.