YJIT Benchmarks

Details for Benchmarks at 2021-12-08 19:10:33

Overall YJIT is 30.8% faster than interpreted CRuby!
On Railsbench specifically, YJIT is 30.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 170 20 170 75 170 20 170
mail 5 138 20 138 75 138 20 138
psych-load 5 15 20 15 75 15 20 15
railsbench 5 15 20 15 75 15 20 15
binarytrees 5 85 20 85 75 85 20 85
erubi 5 52 20 52 75 52 20 52
erubi_rails 5 593 20 593 75 593 20 593
fannkuchredux 5 15 20 15 52 15 20 15
jekyll 5 15 20 15 35 15 20 15
lee 5 26 20 26 75 26 20 26
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 64 20 64 73 64 20 64
30k_methods 5 26 20 26 41 26 20 26
cfunc_itself 5 493 20 493 75 493 20 493
fib 5 383 20 383 75 383 20 383
getivar 5 562 20 562 75 562 20 562
keyword_args 5 439 20 439 75 439 20 439
respond_to 5 131 20 131 75 131 20 131
setivar 5 504 20 504 75 504 20 504

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 757272 185 1194 0 0% 0 0 0
hexapdf (click) 1095978 893337 595 7996 614 7% 0 0 321
liquid-render (click) 492869 389576 143 1438 95 6% 0 0 1
mail (click) 893930 666996 325 5432 124 2% 0 0 39
psych-load (click) 312737 246864 57 435 1 0% 0 0 0
railsbench (click) 2520930 1910843 1295 9293 263 2% 0 0 26
binarytrees (click) 164595 127508 9 49 0 0% 0 0 0
erubi (click) 290913 229454 8 35 0 0% 0 0 0
erubi_rails (click) 2407138 1746413 260 1974 16 0% 0 0 3
fannkuchredux (click) 180595 139518 6 203 0 0% 0 0 0
jekyll (click) 1873770 1508390 336 3741 185 4% 0 0 0
lee (click) 350762 276874 44 562 67 11% 0 0 12
nbody (click) 174003 134709 8 149 0 0% 0 0 0
optcarrot (click) 502835 440245 196 3567 20 0% 0 0 0
rubykon (click) 308659 249755 138 1557 1 0% 0 0 0
30k_ifelse (click) 5553907 4347945 9261 57795 0 0% 0 0 0
30k_methods (click) 2179891 1660857 5780 19418 0 0% 0 0 0
cfunc_itself (click) 163379 126250 6 40 0 0% 0 0 0
fib (click) 161843 125858 6 29 0 0% 0 0 0
getivar (click) 163379 128256 6 56 0 0% 0 0 0
keyword_args (click) 164211 126931 7 42 0 0% 0 0 0
respond_to (click) 165299 127591 6 55 0 0% 0 0 0
setivar (click) 163891 127149 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.