YJIT Benchmarks

Details for Benchmarks at 2021-11-29 07:10:30

Overall YJIT is 27.6% faster than interpreted CRuby!
On Railsbench specifically, YJIT is 21.9% 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 185 20 185 75 185 20 185
hexapdf 5 15 20 15 20 15
liquid-render 5 174 20 174 75 174 20 174
mail 5 140 20 140 75 140 20 140
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 51 20 51 75 51 20 51
erubi_rails 5 570 20 570 75 570 20 570
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 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 62 20 62 67 62 20 62
30k_methods 5 26 20 26 44 26 20 26
cfunc_itself 5 512 20 512 75 512 20 512
fib 5 384 20 384 75 384 20 384
getivar 5 563 20 563 75 563 20 563
keyword_args 5 431 20 431 75 431 20 431
respond_to 5 127 20 127 75 127 20 127
setivar 5 501 20 501 75 501 20 501

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) 971114 730252 185 1187 0 0% 0 0 0
hexapdf (click) 1076970 858162 595 8004 616 7% 0 0 321
liquid-render (click) 467959 363536 143 1433 95 6% 0 0 1
mail (click) 872426 642587 325 5438 124 2% 0 0 39
psych-load (click) 291041 225919 57 423 1 0% 0 0 0
railsbench (click) 2571682 1919144 1293 9694 264 2% 0 0 26
binarytrees (click) 112485 85541 9 48 0 0% 0 0 0
erubi (click) 269153 208860 8 35 0 0% 0 0 0
erubi_rails (click) 2437602 1743070 260 1998 17 0% 0 0 3
fannkuchredux (click) 128293 97418 6 202 0 0% 0 0 0
jekyll (click) 1890026 1501537 336 3999 179 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) 450853 392113 196 3566 20 0% 0 0 0
rubykon (click) 256229 206091 139 1553 1 0% 0 0 0
30k_ifelse (click) 5501797 4306060 9261 57794 0 0% 0 0 0
30k_methods (click) 2116901 1614522 5780 19351 0 0% 0 0 0
cfunc_itself (click) 110885 84037 6 39 0 0% 0 0 0
fib (click) 109925 83994 6 28 0 0% 0 0 0
getivar (click) 111653 86505 6 55 0 0% 0 0 0
keyword_args (click) 112037 85006 7 41 0 0% 0 0 0
respond_to (click) 113573 85840 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.