YJIT Benchmarks

Details for Benchmarks at 2021-12-17 07:11:00

Overall YJIT is 28.6% faster than interpreted CRuby!
On Railsbench specifically, YJIT is 27.5% 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 172 20 172 75 172 20 172
mail 5 138 20 138 75 138 20 138
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 52 20 52 75 52 20 52
erubi_rails 5 605 20 605 75 605 20 605
fannkuchredux 5 15 20 15 52 15 20 15
jekyll 5 15 20 15 36 15 20 15
lee 5 27 20 27 75 27 20 27
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 64 20 64 75 64 20 64
30k_methods 5 27 20 27 42 27 20 27
cfunc_itself 5 490 20 490 75 490 20 490
fib 5 383 20 383 75 383 20 383
getivar 5 564 20 564 75 564 20 564
keyword_args 5 427 20 427 75 427 20 427
respond_to 5 130 20 130 75 130 20 130
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) 972138 740901 185 1194 0 0% 0 0 0
hexapdf (click) 1077098 876885 595 7998 614 7% 0 0 321
liquid-render (click) 468727 370301 143 1431 96 6% 0 0 1
mail (click) 852586 634575 325 5219 124 2% 0 0 39
psych-load (click) 291233 228830 57 423 1 0% 0 0 0
railsbench (click) 2496482 1886742 1295 9260 263 2% 0 0 26
binarytrees (click) 113381 86737 9 48 0 0% 0 0 0
erubi (click) 271393 212679 8 35 0 0% 0 0 0
erubi_rails (click) 2466914 1776976 261 1978 17 0% 0 0 3
fannkuchredux (click) 128805 98418 6 202 0 0% 0 0 0
jekyll (click) 1858218 1494769 336 3759 186 4% 0 0 0
lee (click) 329953 258987 43 557 66 11% 0 0 12
nbody (click) 122853 93938 8 148 0 0% 0 0 0
optcarrot (click) 451045 399145 196 3566 20 0% 0 0 0
rubykon (click) 254437 206596 138 1526 1 0% 0 0 0
30k_ifelse (click) 5501925 4306732 9261 57794 0 0% 0 0 0
30k_methods (click) 2117093 1615194 5780 19351 0 0% 0 0 0
cfunc_itself (click) 111397 85037 6 39 0 0% 0 0 0
fib (click) 110437 84974 6 28 0 0% 0 0 0
getivar (click) 111589 87156 6 55 0 0% 0 0 0
keyword_args (click) 112229 85678 7 41 0 0% 0 0 0
respond_to (click) 114149 86820 6 54 0 0% 0 0 0
setivar (click) 111589 85680 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.