YJIT Benchmarks

Details for Benchmarks at 2021-11-11 07:11:47

Overall YJIT is 29.1% faster than interpreted CRuby!
On Railsbench specifically, YJIT is 19.4% 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 118 10 115 10 168
hexapdf 10 10 10 10 10 10
liquid-render 10 102 10 110 10 158
mail 10 113 10 118 10 129
psych-load 10 10 10 10 10 10
railsbench 10 10 10 10 10 10
binarytrees 10 45 10 70 10 58
fannkuchredux 10 10 10 10 10 10
jekyll 10 10 10 10 10 10
lee 10 10 10 14 10 16
nbody 10 175 10 327 10 257
optcarrot 10 10 10 10 10 10
rubykon 10 10 10 10 10 10
30k_ifelse 10 10 10 10 10 53
30k_methods 10 10 10 10 10 16
cfunc_itself 10 200 10 338 10 501
fib 10 87 10 306 10 373
getivar 10 223 10 211 10 542
keyword_args 10 75 10 97 10 422
respond_to 10 76 10 89 10 119
setivar 10 282 10 261 10 460

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) 969834 678958 184 1172 0 0% 0 0 0
hexapdf (click) 1087594 812761 604 8073 647 8% 0 0 320
liquid-render (click) 467063 340891 143 1424 95 6% 0 0 1
mail (click) 850026 585081 339 5184 124 2% 0 0 39
psych-load (click) 296673 211303 57 423 1 0% 0 0 0
railsbench (click) 2588962 1799146 1295 9698 263 2% 0 0 26
binarytrees (click) 113317 80608 9 48 0 0% 0 0 0
fannkuchredux (click) 129317 92618 6 202 0 0% 0 0 0
jekyll (click) 1886186 1391728 336 3912 179 4% 0 0 0
lee (click) 345194 239795 44 566 70 12% 0 0 12
nbody (click) 122725 87443 8 148 0 0% 0 0 0
optcarrot (click) 451685 381143 196 3566 20 0% 0 0 0
rubykon (click) 256933 198854 139 1553 1 0% 0 0 0
30k_ifelse (click) 5502501 4300932 9261 57794 0 0% 0 0 0
30k_methods (click) 2117029 1609045 5780 19351 0 0% 0 0 0
cfunc_itself (click) 111909 79237 6 39 0 0% 0 0 0
fib (click) 109797 78496 6 28 0 0% 0 0 0
getivar (click) 112101 81356 6 55 0 0% 0 0 0
keyword_args (click) 112741 79878 7 41 0 0% 0 0 0
respond_to (click) 114021 80571 6 54 0 0% 0 0 0
setivar (click) 112037 79880 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.