YJIT Benchmarks

Details for Benchmarks at 2021-12-04 19:10:04

Overall YJIT is 32.5% faster than interpreted CRuby!
On Railsbench specifically, YJIT is 31.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 138 20 138 75 138 20 138
psych-load 5 15 20 15 75 15 20 15
railsbench 5 15 20 15 75 15 20 15
binarytrees 5 88 20 88 75 88 20 88
erubi 5 50 20 50 75 50 20 50
erubi_rails 5 553 20 553 75 553 20 553
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 68 65 20 65
30k_methods 5 26 20 26 43 26 20 26
cfunc_itself 5 485 20 485 75 485 20 485
fib 5 383 20 383 75 383 20 383
getivar 5 562 20 562 75 562 20 562
keyword_args 5 439 20 439 75 439 20 439
respond_to 5 128 20 128 75 128 20 128
setivar 5 475 20 475 75 475 20 475

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) 989930 758506 185 1194 0 0% 0 0 0
hexapdf (click) 1097194 898943 596 8007 614 7% 0 0 321
liquid-render (click) 490885 389896 143 1434 95 6% 0 0 1
mail (click) 894506 668828 325 5447 124 2% 0 0 39
psych-load (click) 311585 247284 57 428 1 0% 0 0 0
railsbench (click) 2521186 1915778 1295 9269 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) 2452130 1775737 260 1989 17 0% 0 0 3
fannkuchredux (click) 179443 139387 6 203 0 0% 0 0 0
jekyll (click) 1877482 1518483 336 3775 185 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) 309683 253833 138 1582 1 0% 0 0 0
30k_ifelse (click) 5552627 4367761 9261 57795 0 0% 0 0 0
30k_methods (click) 2174451 1658661 5780 19394 0 0% 0 0 0
cfunc_itself (click) 162035 126006 6 40 0 0% 0 0 0
fib (click) 160691 125747 6 29 0 0% 0 0 0
getivar (click) 162227 128325 6 56 0 0% 0 0 0
keyword_args (click) 162867 126647 7 42 0 0% 0 0 0
respond_to (click) 164339 127593 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.