YJIT Benchmarks

Details for Benchmarks at 2021-11-03 19:09:49

Overall YJIT is 31.5% faster than interpreted CRuby!
On Railsbench specifically, YJIT is 25.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 YJIT warmups YJIT iters
activerecord 10 125 10 115 10 177
hexapdf 10 10 10 10 10 10
liquid-render 10 104 10 113 10 167
mail 10 116 10 120 10 131
psych-load 10 10 10 10 10 10
railsbench 10 10 10 10 10 10
binarytrees 10 45 10 70 10 60
fannkuchredux 10 10 10 10 10 10
jekyll 10 10 10 10 10 10
lee 10 10 10 12 10 15
nbody 10 172 10 321 10 256
optcarrot 10 10 10 10 10 10
rubykon 10 10 10 10 10 10
30k_ifelse 10 10 10 10 10 52
30k_methods 10 10 10 10 10 17
cfunc_itself 10 207 10 339 10 465
fib 10 93 10 308 10 374
getivar 10 221 10 211 10 530
keyword_args 10 73 10 98 10 421
respond_to 10 80 10 90 10 116
setivar 10 256 10 255 10 492

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) 1121882 875208 185 1159 0 0% 0 0 0
hexapdf (click) 1096500 917500 603 7982 624 7% 0 0 320
liquid-render (click) 474625 388488 143 1428 95 6% 0 0 1
mail (click) 846964 656984 339 5056 124 2% 0 0 39
psych-load (click) 187626 151327 56 409 1 0% 0 0 0
railsbench (click) 2604465 2033114 1295 9603 262 2% 0 0 26
binarytrees (click) 114154 90920 9 48 0 0% 0 0 0
fannkuchredux (click) 130218 104545 6 202 0 0% 0 0 0
jekyll (click) 2025140 1682709 336 3854 180 4% 0 0 0
lee (click) 237162 183246 85 1098 111 10% 1 0 13
nbody (click) 124138 99044 8 148 0 0% 0 0 0
optcarrot (click) 460074 430820 196 3566 20 0% 0 0 0
rubykon (click) 258154 223533 138 1524 1 0% 0 0 0
30k_ifelse (click) 5561770 4891849 9261 57794 0 0% 0 0 0
30k_methods (click) 2118890 1818060 5780 19351 0 0% 0 0 0
cfunc_itself (click) 112618 89359 6 39 0 0% 0 0 0
fib (click) 111658 89326 6 28 0 0% 0 0 0
getivar (click) 113770 92545 6 55 0 0% 0 0 0
keyword_args (click) 113450 90115 7 41 0 0% 0 0 0
respond_to (click) 115370 91267 6 54 0 0% 0 0 0
setivar (click) 113386 90476 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.