YJIT Benchmarks

Details for Benchmarks at 2021-12-11 07:10:36

Overall YJIT is 30.9% faster than interpreted CRuby!
On Railsbench specifically, YJIT is 24.8% 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 191 20 191 75 191 20 191
hexapdf 5 15 20 15 20 15
liquid-render 5 172 20 172 75 172 20 172
mail 5 142 20 142 75 142 20 142
psych-load 5 15 20 15 75 15 20 15
railsbench 5 15 20 15 75 15 20 15
binarytrees 5 84 20 84 75 84 20 84
erubi 5 52 20 52 75 52 20 52
erubi_rails 5 600 20 600 75 600 20 600
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 344 20 344 75 344 20 344
optcarrot 5 15 20 15 75 15 20 15
rubykon 5 15 20 15 43 15 20 15
30k_ifelse 5 62 20 62 71 62 20 62
30k_methods 5 26 20 26 45 26 20 26
cfunc_itself 5 497 20 497 75 497 20 497
fib 5 383 20 383 75 383 20 383
getivar 5 563 20 563 75 563 20 563
keyword_args 5 438 20 438 75 438 20 438
respond_to 5 128 20 128 75 128 20 128
setivar 5 510 20 510 75 510 20 510

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) 990378 757061 185 1194 0 0% 0 0 0
hexapdf (click) 1096042 893104 595 7998 614 7% 0 0 321
liquid-render (click) 490309 387566 143 1400 96 6% 0 0 1
mail (click) 876714 654111 325 5251 124 2% 0 0 39
psych-load (click) 312737 246741 57 435 1 0% 0 0 0
railsbench (click) 2517986 1907907 1295 9271 263 2% 0 0 26
binarytrees (click) 164531 127410 9 49 0 0% 0 0 0
erubi (click) 290849 229356 8 35 0 0% 0 0 0
erubi_rails (click) 2462434 1778912 260 1958 17 0% 0 0 3
fannkuchredux (click) 180531 139420 6 203 0 0% 0 0 0
jekyll (click) 1875626 1509640 336 3735 185 4% 0 0 0
lee (click) 348961 275343 43 557 66 11% 0 0 12
nbody (click) 173939 134611 8 149 0 0% 0 0 0
optcarrot (click) 502771 440147 196 3567 20 0% 0 0 0
rubykon (click) 307891 249047 138 1548 1 0% 0 0 0
30k_ifelse (click) 5553651 4347734 9261 57795 0 0% 0 0 0
30k_methods (click) 2174259 1658202 5780 19386 0 0% 0 0 0
cfunc_itself (click) 163123 126039 6 40 0 0% 0 0 0
fib (click) 161587 125647 6 29 0 0% 0 0 0
getivar (click) 163315 128158 6 56 0 0% 0 0 0
keyword_args (click) 163955 126680 7 42 0 0% 0 0 0
respond_to (click) 165235 127493 6 55 0 0% 0 0 0
setivar (click) 163251 126682 6 29 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.