YJIT Benchmarks

Details for Benchmarks at 2021-10-25 19:09:28

Overall YJIT is 26.4% faster than interpreted CRuby!
On Railsbench specifically, YJIT is 19.1% 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 128 10 119 10 177
hexapdf 10 10 10 10 10 10
liquid-render 10 106 10 109 10 143
mail 10 118 10 123 10 132
psych-load 10 10 10 10 10 10
railsbench 10 10 10 10 10 10
binarytrees 10 44 10 70 10 57
fannkuchredux 10 10 10 10 10 10
jekyll 10 10 10 10 10 10
lee 10 10 10 13 10 16
nbody 10 175 10 324 10 256
optcarrot 10 10 10 10 10 10
rubykon 10 10 10 10 10 10
30k_ifelse 10 10 10 10 10 50
30k_methods 10 10 10 10 10 17
cfunc_itself 10 205 10 334 10 502
fib 10 92 10 307 10 375
getivar 10 209 10 211 10 529
keyword_args 10 74 10 97 10 429
respond_to 10 76 10 90 10 111
setivar 10 273 10 265 10 458

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) 1118042 871765 185 1172 0 0% 0 0 0
hexapdf (click) 1077492 902620 603 7827 621 7% 0 0 320
liquid-render (click) 460052 376318 143 1272 94 7% 0 0 1
mail (click) 847156 657306 339 5170 124 2% 0 0 39
psych-load (click) 192874 156132 56 409 1 0% 0 0 0
railsbench (click) 2574961 2010741 1293 9500 262 2% 0 0 26
binarytrees (click) 113469 89958 9 49 0 0% 0 0 0
fannkuchredux (click) 130858 104636 6 202 0 0% 0 0 0
jekyll (click) 1967898 1636818 336 3788 173 4% 0 0 0
lee (click) 235050 181701 85 1082 114 10% 1 0 13
nbody (click) 123325 97934 8 149 0 0% 0 0 0
optcarrot (click) 459325 429858 196 3567 20 0% 0 0 0
rubykon (click) 256938 221921 138 1511 1 0% 0 0 0
30k_ifelse (click) 5561149 4890755 9261 57795 0 0% 0 0 0
30k_methods (click) 2117117 1816178 5780 19352 0 0% 0 0 0
cfunc_itself (click) 113322 89450 6 39 0 0% 0 0 0
fib (click) 110845 88216 6 29 0 0% 0 0 0
getivar (click) 112573 91057 6 56 0 0% 0 0 0
keyword_args (click) 112829 89021 7 42 0 0% 0 0 0
respond_to (click) 115498 90994 6 54 0 0% 0 0 0
setivar (click) 113578 90173 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.