YJIT Benchmarks

Details for Benchmarks at 2022-03-04 19:12:10

Overall YJIT is 32.0% faster than interpreted CRuby!
On Railsbench specifically, YJIT is 30.0% 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 MJIT warmups MJIT iters YJIT warmups YJIT iters
activerecord 5 178 75 178 20 178
hexapdf 5 15 20 15
liquid-render 5 152 75 152 20 152
mail 5 122 75 122 20 122
psych-load 5 15 75 15 20 15
railsbench 5 15 75 15 20 15
binarytrees 5 75 75 75 20 75
discourse 5 33 75 33 20 33
erubi 5 47 75 47 20 47
erubi_rails 5 962 75 962 20 962
fannkuchredux 5 15 75 15 20 15
lee 5 21 75 21 20 21
nbody 5 287 75 287 20 287
optcarrot 5 15 75 15 20 15
rubykon 5 15 37 15 20 15
30k_ifelse 5 55 75 55 20 55
30k_methods 5 22 30 22 20 22
cfunc_itself 5 445 75 445 20 445
fib 5 320 75 320 20 320
getivar 5 769 75 769 20 769
keyword_args 5 370 75 370 20 370
respond_to 5 108 75 108 20 108
setivar 5 1683 75 1683 20 1683

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) 988049 756603 185 1205 0 0% 0 0 0
hexapdf (click) 1113617 912235 599 8170 613 7% 0 0 320
liquid-render (click) 486161 385050 143 1565 95 6% 0 0 1
mail (click) 870545 652081 324 5271 125 2% 0 0 39
psych-load (click) 329489 260378 59 434 1 0% 0 0 0
railsbench (click) 2531473 1928903 1297 9342 268 2% 0 0 26
binarytrees (click) 150481 115115 11 59 0 0% 0 0 0
discourse (click) 22393105 11267319 3147 280775 257005 91% 2 0 133
erubi (click) 320977 254037 10 79 0 0% 0 0 0
erubi_rails (click) 1901521 1431188 262 1877 18 0% 0 0 3
fannkuchredux (click) 164689 126500 8 189 0 0% 0 0 0
lee (click) 369745 290353 45 587 69 11% 0 0 12
nbody (click) 160081 122890 10 159 0 0% 0 0 0
optcarrot (click) 487313 428520 198 3576 20 0% 0 0 0
rubykon (click) 284497 228846 140 1540 1 0% 0 0 0
30k_ifelse (click) 5531665 4328411 9263 57805 0 0% 0 0 0
30k_methods (click) 2154705 1643901 5782 19362 0 0% 0 0 0
cfunc_itself (click) 140945 106603 8 50 0 0% 0 0 0
fib (click) 147857 113926 8 39 0 0% 0 0 0
getivar (click) 149265 115863 8 66 0 0% 0 0 0
keyword_args (click) 150289 115072 9 52 0 0% 0 0 0
respond_to (click) 151249 115311 8 65 0 0% 0 0 0
setivar (click) 149777 114716 8 39 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.