YJIT Benchmarks

Details for Benchmarks at 2021-11-28 07:10:07

Overall YJIT is 29.2% faster than interpreted CRuby!
On Railsbench specifically, YJIT is 23.2% 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 187 20 187 75 187 20 187
hexapdf 5 15 20 15 20 15
liquid-render 5 173 20 173 75 173 20 173
mail 5 139 20 139 75 139 20 139
psych-load 5 15 20 15 75 15 20 15
railsbench 5 15 20 15 75 15 20 15
binarytrees 5 85 20 85 75 85 20 85
erubi 5 50 20 50 75 50 20 50
erubi_rails 5 590 20 590 75 590 20 590
fannkuchredux 5 15 20 15 55 15 20 15
jekyll 5 15 20 15 35 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 44 15 20 15
30k_ifelse 5 65 20 65 75 65 20 65
30k_methods 5 26 20 26 43 26 20 26
cfunc_itself 5 511 20 511 75 511 20 511
fib 5 384 20 384 75 384 20 384
getivar 5 563 20 563 75 563 20 563
keyword_args 5 432 20 432 75 432 20 432
respond_to 5 128 20 128 75 128 20 128
setivar 5 510 20 510 75 510 20 510

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) 968490 728237 185 1175 0 0% 0 0 0
hexapdf (click) 1076010 857487 595 7993 616 7% 0 0 321
liquid-render (click) 463735 360907 143 1395 95 6% 0 0 1
mail (click) 852906 628874 325 5237 124 2% 0 0 39
psych-load (click) 291489 226160 57 423 1 0% 0 0 0
railsbench (click) 2564002 1913863 1293 9631 263 2% 0 0 26
binarytrees (click) 112293 85408 9 48 0 0% 0 0 0
erubi (click) 269153 208542 8 35 0 0% 0 0 0
erubi_rails (click) 2440802 1745451 260 1997 17 0% 0 0 3
fannkuchredux (click) 128293 97418 6 202 0 0% 0 0 0
jekyll (click) 1884906 1498627 336 3958 180 4% 0 0 0
lee (click) 330218 256770 44 562 67 11% 0 0 12
nbody (click) 121701 92379 8 148 0 0% 0 0 0
optcarrot (click) 450533 391785 196 3566 20 0% 0 0 0
rubykon (click) 253797 203698 139 1521 1 0% 0 0 0
30k_ifelse (click) 5501797 4306060 9261 57794 0 0% 0 0 0
30k_methods (click) 2116581 1614194 5780 19351 0 0% 0 0 0
cfunc_itself (click) 111781 84714 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) 111909 84811 7 41 0 0% 0 0 0
respond_to (click) 112997 85491 6 54 0 0% 0 0 0
setivar (click) 111589 85029 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.