YJIT Benchmarks

Details for Benchmarks at 2021-11-29 19:10:57

Overall YJIT is 29.9% faster than interpreted CRuby!
On Railsbench specifically, YJIT is 22.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 190 20 190 75 190 20 190
hexapdf 5 15 20 15 20 15
liquid-render 5 167 20 167 75 167 20 167
mail 5 136 20 136 75 136 20 136
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 50 20 50 75 50 20 50
erubi_rails 5 574 20 574 75 574 20 574
fannkuchredux 5 15 20 15 55 15 20 15
jekyll 5 15 20 15 36 15 20 15
lee 5 26 20 26 75 26 20 26
nbody 5 343 20 343 75 343 20 343
optcarrot 5 15 20 15 75 15 20 15
rubykon 5 15 20 15 43 15 20 15
30k_ifelse 5 64 20 64 69 64 20 64
30k_methods 5 26 20 26 43 26 20 26
cfunc_itself 5 511 20 511 75 511 20 511
fib 5 383 20 383 75 383 20 383
getivar 5 563 20 563 75 563 20 563
keyword_args 5 435 20 435 75 435 20 435
respond_to 5 127 20 127 75 127 20 127
setivar 5 509 20 509 75 509 20 509

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) 970666 729662 185 1183 0 0% 0 0 0
hexapdf (click) 1075626 857109 595 7993 614 7% 0 0 321
liquid-render (click) 466551 362878 143 1428 95 6% 0 0 1
mail (click) 871402 641874 325 5430 124 2% 0 0 39
psych-load (click) 291809 226488 57 423 1 0% 0 0 0
railsbench (click) 2577314 1923125 1293 9742 263 2% 0 0 26
binarytrees (click) 112613 85736 9 48 0 0% 0 0 0
erubi (click) 268705 208266 8 35 0 0% 0 0 0
erubi_rails (click) 2435426 1740990 260 1974 17 0% 0 0 3
fannkuchredux (click) 128293 97418 6 202 0 0% 0 0 0
jekyll (click) 1888234 1500712 336 3996 179 4% 0 0 0
lee (click) 330218 256770 44 562 67 11% 0 0 12
nbody (click) 122213 92840 8 148 0 0% 0 0 0
optcarrot (click) 450853 392113 196 3566 20 0% 0 0 0
rubykon (click) 257189 206594 138 1560 1 0% 0 0 0
30k_ifelse (click) 5501989 4306193 9261 57794 0 0% 0 0 0
30k_methods (click) 2116581 1614194 5780 19351 0 0% 0 0 0
cfunc_itself (click) 111205 84365 6 39 0 0% 0 0 0
fib (click) 109669 83973 6 28 0 0% 0 0 0
getivar (click) 111397 86484 6 55 0 0% 0 0 0
keyword_args (click) 112037 85006 7 41 0 0% 0 0 0
respond_to (click) 112997 85491 6 54 0 0% 0 0 0
setivar (click) 111013 84680 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.