YJIT Benchmarks

Details for Benchmarks at 2021-12-03 07:11:04

Overall YJIT is 28.0% faster than interpreted CRuby!
On Railsbench specifically, YJIT is 29.9% 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 185 20 185 75 185 20 185
hexapdf 5 15 20 15 20 15
liquid-render 5 170 20 170 75 170 20 170
mail 5 139 20 139 75 139 20 139
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 50 20 50 75 50 20 50
erubi_rails 5 572 20 572 75 572 20 572
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 343 20 343 75 343 20 343
optcarrot 5 15 20 15 75 15 20 15
rubykon 5 15 20 15 43 15 20 15
30k_ifelse 5 64 20 64 74 64 20 64
30k_methods 5 26 20 26 42 26 20 26
cfunc_itself 5 505 20 505 75 505 20 505
fib 5 383 20 383 75 383 20 383
getivar 5 562 20 562 75 562 20 562
keyword_args 5 440 20 440 75 440 20 440
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) 990122 745849 185 1194 0 0% 0 0 0
hexapdf (click) 1095530 873842 595 7993 614 7% 0 0 321
liquid-render (click) 493125 383283 143 1458 95 6% 0 0 1
mail (click) 893482 660057 325 5437 124 2% 0 0 39
psych-load (click) 311905 243047 57 428 1 0% 0 0 0
railsbench (click) 2519010 1886942 1295 9247 264 2% 0 0 26
binarytrees (click) 163699 125398 9 49 0 0% 0 0 0
erubi (click) 290721 226331 8 35 0 0% 0 0 0
erubi_rails (click) 2450722 1754279 260 1985 17 0% 0 0 3
fannkuchredux (click) 179315 137192 6 203 0 0% 0 0 0
jekyll (click) 1877674 1490193 336 3742 184 4% 0 0 0
lee (click) 349226 272210 44 562 67 11% 0 0 12
nbody (click) 173107 132369 8 149 0 0% 0 0 0
optcarrot (click) 501619 431754 196 3567 20 0% 0 0 0
rubykon (click) 304435 243241 138 1519 1 0% 0 0 0
30k_ifelse (click) 5552883 4345722 9261 57795 0 0% 0 0 0
30k_methods (click) 2167859 1654296 5780 19352 0 0% 0 0 0
cfunc_itself (click) 162163 124139 6 40 0 0% 0 0 0
fib (click) 160499 123614 6 29 0 0% 0 0 0
getivar (click) 162227 126125 6 56 0 0% 0 0 0
keyword_args (click) 162867 124647 7 42 0 0% 0 0 0
respond_to (click) 164339 125481 6 55 0 0% 0 0 0
setivar (click) 162163 124649 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.