YJIT Benchmarks

Details for Benchmarks at 2021-12-07 07:10:47

Overall YJIT is 30.5% faster than interpreted CRuby!
On Railsbench specifically, YJIT is 26.2% 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 189 20 189 75 189 20 189
hexapdf 5 15 20 15 20 15
liquid-render 5 171 20 171 75 171 20 171
mail 5 140 20 140 75 140 20 140
psych-load 5 15 20 15 75 15 20 15
railsbench 5 15 20 15 75 15 20 15
binarytrees 5 88 20 88 75 88 20 88
erubi 5 52 20 52 75 52 20 52
erubi_rails 5 618 20 618 75 618 20 618
fannkuchredux 5 15 20 15 53 15 20 15
jekyll 5 15 20 15 35 15 20 15
lee 5 26 20 26 75 26 20 26
nbody 5 341 20 341 75 341 20 341
optcarrot 5 15 20 15 75 15 20 15
rubykon 5 15 20 15 43 15 20 15
30k_ifelse 5 65 20 65 75 65 20 65
30k_methods 5 27 20 27 44 27 20 27
cfunc_itself 5 513 20 513 75 513 20 513
fib 5 383 20 383 75 383 20 383
getivar 5 562 20 562 75 562 20 562
keyword_args 5 436 20 436 75 436 20 436
respond_to 5 130 20 130 75 130 20 130
setivar 5 480 20 480 75 480 20 480

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) 989162 757760 185 1193 0 0% 0 0 0
hexapdf (click) 1096106 897933 596 8004 614 7% 0 0 321
liquid-render (click) 491525 390042 143 1436 95 6% 0 0 1
mail (click) 887530 664203 325 5389 124 2% 0 0 39
psych-load (click) 310945 246525 57 429 1 0% 0 0 0
railsbench (click) 2522402 1916629 1295 9292 263 2% 0 0 26
binarytrees (click) 163507 127265 9 49 0 0% 0 0 0
erubi (click) 289825 229351 8 35 0 0% 0 0 0
erubi_rails (click) 2409442 1753624 260 1969 16 0% 0 0 3
fannkuchredux (click) 179507 139275 6 203 0 0% 0 0 0
jekyll (click) 1873578 1515972 336 3751 185 4% 0 0 0
lee (click) 350186 276935 44 562 67 11% 0 0 12
nbody (click) 173043 134809 8 149 0 0% 0 0 0
optcarrot (click) 501683 449482 196 3567 20 0% 0 0 0
rubykon (click) 305459 249789 138 1524 1 0% 0 0 0
30k_ifelse (click) 5553267 4367998 9261 57795 0 0% 0 0 0
30k_methods (click) 2167795 1656071 5780 19352 0 0% 0 0 0
cfunc_itself (click) 162099 125894 6 40 0 0% 0 0 0
fib (click) 160499 125502 6 29 0 0% 0 0 0
getivar (click) 162419 128386 6 56 0 0% 0 0 0
keyword_args (click) 163507 126924 7 42 0 0% 0 0 0
respond_to (click) 164211 127348 6 55 0 0% 0 0 0
setivar (click) 162227 126537 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.