YJIT Benchmarks

Details for Benchmarks at 2021-12-05 07:10:25

Overall YJIT is 28.6% faster than interpreted CRuby!
On Railsbench specifically, YJIT is 25.4% 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 190 20 190 75 190 20 190
hexapdf 5 15 20 15 20 15
liquid-render 5 174 20 174 75 174 20 174
mail 5 140 20 140 75 140 20 140
psych-load 5 15 20 15 75 15 20 15
railsbench 5 15 20 15 75 15 20 15
binarytrees 5 86 20 86 75 86 20 86
erubi 5 48 20 48 75 48 20 48
erubi_rails 5 572 20 572 75 572 20 572
fannkuchredux 5 15 20 15 52 15 20 15
jekyll 5 15 20 15 35 15 20 15
lee 5 25 20 25 75 25 20 25
nbody 5 341 20 341 75 341 20 341
optcarrot 5 15 20 15 75 15 20 15
rubykon 5 15 20 15 43 15 20 15
30k_ifelse 5 64 20 64 72 64 20 64
30k_methods 5 26 20 26 43 26 20 26
cfunc_itself 5 517 20 517 75 517 20 517
fib 5 383 20 383 75 383 20 383
getivar 5 562 20 562 75 562 20 562
keyword_args 5 431 20 431 75 431 20 431
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) 989802 758373 185 1194 0 0% 0 0 0
hexapdf (click) 1095530 897920 595 7994 614 7% 0 0 321
liquid-render (click) 489925 389254 143 1418 95 6% 0 0 1
mail (click) 875626 654996 325 5243 124 2% 0 0 39
psych-load (click) 311329 246976 57 429 1 0% 0 0 0
railsbench (click) 2524002 1917859 1295 9296 263 2% 0 0 26
binarytrees (click) 163443 127377 9 49 0 0% 0 0 0
erubi (click) 291041 230499 8 35 0 0% 0 0 0
erubi_rails (click) 2416802 1760257 260 1990 16 0% 0 0 3
fannkuchredux (click) 179123 139039 6 203 0 0% 0 0 0
jekyll (click) 1877034 1518526 336 3772 186 4% 0 0 0
lee (click) 349546 276698 44 562 67 11% 0 0 12
nbody (click) 172851 134748 8 149 0 0% 0 0 0
optcarrot (click) 501683 449594 196 3567 20 0% 0 0 0
rubykon (click) 305523 250066 138 1530 1 0% 0 0 0
30k_ifelse (click) 5552627 4367761 9261 57795 0 0% 0 0 0
30k_methods (click) 2167731 1656183 5780 19352 0 0% 0 0 0
cfunc_itself (click) 162611 126355 6 40 0 0% 0 0 0
fib (click) 160499 125614 6 29 0 0% 0 0 0
getivar (click) 162227 128325 6 56 0 0% 0 0 0
keyword_args (click) 163059 126780 7 42 0 0% 0 0 0
respond_to (click) 164147 127460 6 55 0 0% 0 0 0
setivar (click) 162739 126998 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.