YJIT Benchmarks

Details for Benchmarks at 2021-10-26 07:10:02

Overall YJIT is 27.8% faster than interpreted CRuby!
On Railsbench specifically, YJIT is 20.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 131 10 117 10 176
hexapdf 10 10 10 10 10 10
liquid-render 10 102 10 111 10 144
mail 10 113 10 123 10 134
psych-load 10 10 10 10 10 10
railsbench 10 10 10 10 10 10
binarytrees 10 44 10 69 10 57
fannkuchredux 10 10 10 10 10 10
jekyll 10 10 10 10 10 10
lee 10 10 10 13 10 15
nbody 10 176 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 53
30k_methods 10 10 10 10 10 17
cfunc_itself 10 204 10 338 10 492
fib 10 90 10 301 10 375
getivar 10 212 10 211 10 529
keyword_args 10 75 10 97 10 430
respond_to 10 75 10 88 10 111
setivar 10 287 10 264 10 457

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) 1118426 871745 185 1172 0 0% 0 0 0
hexapdf (click) 1077364 902404 603 7814 619 7% 0 0 320
liquid-render (click) 459265 376055 143 1267 94 7% 0 0 1
mail (click) 831860 644187 339 5005 124 2% 0 0 39
psych-load (click) 193002 156260 56 414 1 0% 0 0 0
railsbench (click) 2583857 2017808 1293 9563 262 2% 0 0 26
binarytrees (click) 114410 90765 9 48 0 0% 0 0 0
fannkuchredux (click) 130538 104258 6 202 0 0% 0 0 0
jekyll (click) 1962906 1632470 336 3775 174 4% 0 0 0
lee (click) 235050 181701 85 1082 114 10% 1 0 13
nbody (click) 123754 98495 8 148 0 0% 0 0 0
optcarrot (click) 460714 430911 196 3566 20 0% 0 0 0
rubykon (click) 255594 220910 138 1502 1 0% 0 0 0
30k_ifelse (click) 5562410 4891940 9261 57794 0 0% 0 0 0
30k_methods (click) 2118634 1817379 5780 19351 0 0% 0 0 0
cfunc_itself (click) 113322 89450 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) 114090 90206 7 41 0 0% 0 0 0
respond_to (click) 114794 90370 6 54 0 0% 0 0 0
setivar (click) 113130 89927 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.