YJIT Benchmarks

Details for Benchmarks at 2021-12-26 07:09:54

Overall YJIT is 26.3% faster than interpreted CRuby!
On Railsbench specifically, YJIT is 31.1% 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 188 20 188 75 188 20 188
hexapdf 5 15 20 15 20 15
liquid-render 5 156 20 156 75 156 20 156
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 86 20 86 75 86 20 86
erubi 5 52 20 52 75 52 20 52
erubi_rails 5 573 20 573 75 573 20 573
fannkuchredux 5 15 20 15 54 15 20 15
jekyll 5 15 20 15 36 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 64 20 64 75 64 20 64
30k_methods 5 27 20 27 44 27 20 27
cfunc_itself 5 487 20 487 75 487 20 487
fib 5 384 20 384 75 384 20 384
getivar 5 564 20 564 75 564 20 564
keyword_args 5 432 20 432 75 432 20 432
respond_to 5 129 20 129 75 129 20 129
setivar 5 478 20 478 75 478 20 478

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) 978410 745975 185 1188 0 0% 0 0 0
hexapdf (click) 1123050 917432 599 8116 620 7% 0 0 321
liquid-render (click) 471223 372477 143 1441 95 6% 0 0 1
mail (click) 870506 646452 325 5440 124 2% 0 0 39
psych-load (click) 299553 235946 57 423 1 0% 0 0 0
railsbench (click) 2518562 1904377 1295 9297 266 2% 0 0 26
binarytrees (click) 113445 86913 9 48 0 0% 0 0 0
erubi (click) 279009 219396 8 35 0 0% 0 0 0
erubi_rails (click) 2460066 1772892 260 1952 17 0% 0 0 3
fannkuchredux (click) 128933 98594 6 202 0 0% 0 0 0
jekyll (click) 1846954 1484335 338 3746 185 4% 0 0 0
lee (click) 337121 265463 43 557 70 12% 0 0 12
nbody (click) 123173 94278 8 148 0 0% 0 0 0
optcarrot (click) 451685 399710 196 3566 20 0% 0 0 0
rubykon (click) 257061 208928 138 1547 1 0% 0 0 0
30k_ifelse (click) 5502053 4306908 9261 57794 0 0% 0 0 0
30k_methods (click) 2117349 1615483 5780 19351 0 0% 0 0 0
cfunc_itself (click) 111653 85326 6 39 0 0% 0 0 0
fib (click) 109989 84821 6 28 0 0% 0 0 0
getivar (click) 111845 87445 6 55 0 0% 0 0 0
keyword_args (click) 112485 85967 7 41 0 0% 0 0 0
respond_to (click) 114469 87160 6 54 0 0% 0 0 0
setivar (click) 111781 85969 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.