YJIT Benchmarks

Details for Benchmarks at 2021-12-09 07:10:44

Overall YJIT is 31.6% faster than interpreted CRuby!
On Railsbench specifically, YJIT is 28.7% 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 191 20 191 75 191 20 191
hexapdf 5 15 20 15 20 15
liquid-render 5 167 20 167 75 167 20 167
mail 5 141 20 141 75 141 20 141
psych-load 5 15 20 15 75 15 20 15
railsbench 5 15 20 15 75 15 20 15
binarytrees 5 87 20 87 75 87 20 87
erubi 5 52 20 52 75 52 20 52
erubi_rails 5 620 20 620 75 620 20 620
fannkuchredux 5 15 20 15 51 15 20 15
jekyll 5 15 20 15 36 15 20 15
lee 5 26 20 26 75 26 20 26
nbody 5 343 20 343 75 343 20 343
optcarrot 5 15 20 15 75 15 20 15
rubykon 5 15 20 15 44 15 20 15
30k_ifelse 5 62 20 62 75 62 20 62
30k_methods 5 27 20 27 41 27 20 27
cfunc_itself 5 491 20 491 75 491 20 491
fib 5 383 20 383 75 383 20 383
getivar 5 562 20 562 75 562 20 562
keyword_args 5 434 20 434 75 434 20 434
respond_to 5 131 20 131 75 131 20 131
setivar 5 505 20 505 75 505 20 505

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) 990122 756996 185 1194 0 0% 0 0 0
hexapdf (click) 1096362 893267 595 7997 614 7% 0 0 321
liquid-render (click) 494405 390718 143 1462 95 6% 0 0 1
mail (click) 853802 638390 325 5026 124 2% 0 0 39
psych-load (click) 312993 246919 57 436 1 0% 0 0 0
railsbench (click) 2514658 1905712 1295 9234 263 2% 0 0 26
binarytrees (click) 164467 127410 9 49 0 0% 0 0 0
erubi (click) 290849 229356 8 35 0 0% 0 0 0
erubi_rails (click) 2445794 1765614 260 1938 17 0% 0 0 3
fannkuchredux (click) 180467 139420 6 203 0 0% 0 0 0
jekyll (click) 1879210 1513266 336 3781 186 4% 0 0 0
lee (click) 355178 280423 44 562 67 11% 0 0 12
nbody (click) 173875 134611 8 149 0 0% 0 0 0
optcarrot (click) 502963 440300 196 3567 20 0% 0 0 0
rubykon (click) 305971 247587 138 1525 1 0% 0 0 0
30k_ifelse (click) 5553651 4347734 9261 57795 0 0% 0 0 0
30k_methods (click) 2169907 1656853 5780 19358 0 0% 0 0 0
cfunc_itself (click) 163123 126039 6 40 0 0% 0 0 0
fib (click) 161587 125647 6 29 0 0% 0 0 0
getivar (click) 163315 128158 6 56 0 0% 0 0 0
keyword_args (click) 164147 126793 7 42 0 0% 0 0 0
respond_to (click) 165171 127493 6 55 0 0% 0 0 0
setivar (click) 163827 127011 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.