YJIT Benchmarks

Details for Benchmarks at 2021-12-14 19:11:03

Overall YJIT is 30.9% faster than interpreted CRuby!
On Railsbench specifically, YJIT is 27.6% 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 186 20 186 75 186 20 186
hexapdf 5 15 20 15 20 15
liquid-render 5 175 20 175 75 175 20 175
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 635 20 635 75 635 20 635
fannkuchredux 5 15 20 15 53 15 20 15
jekyll 5 15 20 15 36 15 20 15
lee 5 26 20 26 75 26 20 26
nbody 5 342 20 342 75 342 20 342
optcarrot 5 15 20 15 75 15 20 15
rubykon 5 15 20 15 44 15 20 15
30k_ifelse 5 65 20 65 75 65 20 65
30k_methods 5 27 20 27 43 27 20 27
cfunc_itself 5 503 20 503 75 503 20 503
fib 5 382 20 382 75 382 20 382
getivar 5 563 20 563 75 563 20 563
keyword_args 5 439 20 439 75 439 20 439
respond_to 5 124 20 124 75 124 20 124
setivar 5 479 20 479 75 479 20 479

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) 990314 757127 185 1194 0 0% 0 0 0
hexapdf (click) 1096106 893222 595 7999 614 7% 0 0 321
liquid-render (click) 490437 387898 143 1418 95 6% 0 0 1
mail (click) 892714 666318 325 5428 124 2% 0 0 39
psych-load (click) 312737 246741 57 435 1 0% 0 0 0
railsbench (click) 2519906 1909833 1295 9287 263 2% 0 0 26
binarytrees (click) 164531 127410 9 49 0 0% 0 0 0
erubi (click) 291041 229536 8 35 0 0% 0 0 0
erubi_rails (click) 2417634 1755060 260 1959 16 0% 0 0 3
fannkuchredux (click) 180531 139420 6 203 0 0% 0 0 0
jekyll (click) 1878314 1511934 336 3751 185 4% 0 0 0
lee (click) 348961 275343 43 557 66 11% 0 0 12
nbody (click) 173939 134611 8 149 0 0% 0 0 0
optcarrot (click) 502771 440147 196 3567 20 0% 0 0 0
rubykon (click) 306675 247957 138 1532 1 0% 0 0 0
30k_ifelse (click) 5553651 4347734 9261 57795 0 0% 0 0 0
30k_methods (click) 2174643 1659456 5780 19392 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) 163955 126680 7 42 0 0% 0 0 0
respond_to (click) 165235 127493 6 55 0 0% 0 0 0
setivar (click) 163251 126682 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.