YJIT Benchmarks

Details for Benchmarks at 2021-12-06 07:10:43

Overall YJIT is 28.0% 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 189 20 189 75 189 20 189
hexapdf 5 15 20 15 20 15
liquid-render 5 168 20 168 75 168 20 168
mail 5 137 20 137 75 137 20 137
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 51 20 51 75 51 20 51
erubi_rails 5 554 20 554 75 554 20 554
fannkuchredux 5 15 20 15 52 15 20 15
jekyll 5 15 20 15 35 15 20 15
lee 5 26 20 26 75 26 20 26
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 65 20 65 72 65 20 65
30k_methods 5 26 20 26 44 26 20 26
cfunc_itself 5 518 20 518 75 518 20 518
fib 5 383 20 383 75 383 20 383
getivar 5 561 20 561 75 561 20 561
keyword_args 5 439 20 439 75 439 20 439
respond_to 5 130 20 130 75 130 20 130
setivar 5 477 20 477 75 477 20 477

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) 988714 757480 185 1189 0 0% 0 0 0
hexapdf (click) 1096618 898550 596 7999 614 7% 0 0 321
liquid-render (click) 488197 387995 143 1400 95 6% 0 0 1
mail (click) 893162 667864 325 5434 124 2% 0 0 39
psych-load (click) 311777 247417 57 428 1 0% 0 0 0
railsbench (click) 2525986 1919371 1295 9311 263 2% 0 0 26
binarytrees (click) 163443 127377 9 49 0 0% 0 0 0
erubi (click) 290465 230150 8 35 0 0% 0 0 0
erubi_rails (click) 2447458 1771952 260 1950 17 0% 0 0 3
fannkuchredux (click) 179443 139387 6 203 0 0% 0 0 0
jekyll (click) 1877290 1518766 336 3744 185 4% 0 0 0
lee (click) 349546 276723 44 562 67 11% 0 0 12
nbody (click) 173043 134881 8 149 0 0% 0 0 0
optcarrot (click) 501683 449594 196 3567 20 0% 0 0 0
rubykon (click) 305715 250097 138 1526 1 0% 0 0 0
30k_ifelse (click) 5552563 4367761 9261 57795 0 0% 0 0 0
30k_methods (click) 2167731 1656183 5780 19352 0 0% 0 0 0
cfunc_itself (click) 162547 126355 6 40 0 0% 0 0 0
fib (click) 161075 125963 6 29 0 0% 0 0 0
getivar (click) 162227 128325 6 56 0 0% 0 0 0
keyword_args (click) 162803 126647 7 42 0 0% 0 0 0
respond_to (click) 164659 127809 6 55 0 0% 0 0 0
setivar (click) 162163 126649 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.