YJIT Benchmarks

Details for Benchmarks at 2021-12-22 07:11:19

Overall YJIT is 29.4% faster than interpreted CRuby!
On Railsbench specifically, YJIT is 25.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 188 20 188 75 188 20 188
hexapdf 5 15 20 15 20 15
liquid-render 5 173 20 173 75 173 20 173
mail 5 141 20 141 75 141 20 141
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 53 20 53 75 53 20 53
erubi_rails 5 608 20 608 75 608 20 608
fannkuchredux 5 15 20 15 55 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 44 15 20 15
30k_ifelse 5 65 20 65 75 65 20 65
30k_methods 5 27 20 27 43 27 20 27
cfunc_itself 5 535 20 535 75 535 20 535
fib 5 384 20 384 75 384 20 384
getivar 5 564 20 564 75 564 20 564
keyword_args 5 457 20 457 75 457 20 457
respond_to 5 126 20 126 75 126 20 126
setivar 5 476 20 476 75 476 20 476

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) 974250 742711 185 1194 0 0% 0 0 0
hexapdf (click) 1121386 915400 598 8130 620 7% 0 0 321
liquid-render (click) 473015 373087 143 1469 96 6% 0 0 1
mail (click) 862442 640864 325 5393 124 2% 0 0 39
psych-load (click) 295969 232783 57 423 1 0% 0 0 0
railsbench (click) 2512738 1899765 1295 9297 266 2% 0 0 26
binarytrees (click) 112997 86598 9 48 0 0% 0 0 0
erubi (click) 275809 216449 8 35 0 0% 0 0 0
erubi_rails (click) 2456546 1769929 260 1968 17 0% 0 0 3
fannkuchredux (click) 128485 98279 6 202 0 0% 0 0 0
jekyll (click) 1851626 1487683 338 3781 185 4% 0 0 0
lee (click) 333665 262403 43 557 66 11% 0 0 12
nbody (click) 122021 93583 8 148 0 0% 0 0 0
optcarrot (click) 451621 399611 196 3566 20 0% 0 0 0
rubykon (click) 253925 206111 138 1520 1 0% 0 0 0
30k_ifelse (click) 5501733 4306706 9261 57794 0 0% 0 0 0
30k_methods (click) 2117285 1615384 5780 19351 0 0% 0 0 0
cfunc_itself (click) 111589 85227 6 39 0 0% 0 0 0
fib (click) 110053 84835 6 28 0 0% 0 0 0
getivar (click) 111717 87346 6 55 0 0% 0 0 0
keyword_args (click) 112421 85868 7 41 0 0% 0 0 0
respond_to (click) 113701 86681 6 54 0 0% 0 0 0
setivar (click) 111205 85541 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.