YJIT Benchmarks

Details for Benchmarks at 2021-12-02 07:11:00

Overall YJIT is 30.4% faster than interpreted CRuby!
On Railsbench specifically, YJIT is 21.6% 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 176 20 176 75 176 20 176
hexapdf 5 15 20 15 20 15
liquid-render 5 163 20 163 75 163 20 163
mail 5 134 20 134 75 134 20 134
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 47 20 47 75 47 20 47
erubi_rails 5 526 20 526 75 526 20 526
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 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 62 20 62 61 62 20 62
30k_methods 5 27 20 27 43 27 20 27
cfunc_itself 5 473 20 473 75 473 20 473
fib 5 383 20 383 75 383 20 383
getivar 5 562 20 562 75 562 20 562
keyword_args 5 428 20 428 75 428 20 428
respond_to 5 124 20 124 75 124 20 124
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) 992362 747680 185 1194 0 0% 0 0 0
hexapdf (click) 1094378 872796 595 7994 614 7% 0 0 321
liquid-render (click) 490629 381097 143 1436 95 6% 0 0 1
mail (click) 890154 657952 325 5430 124 2% 0 0 39
psych-load (click) 311841 242644 57 436 1 0% 0 0 0
railsbench (click) 2592354 1936044 1293 9699 263 2% 0 0 26
binarytrees (click) 163699 125398 9 49 0 0% 0 0 0
erubi (click) 288865 224826 8 35 0 0% 0 0 0
erubi_rails (click) 2417314 1739293 260 1981 16 0% 0 0 3
fannkuchredux (click) 179699 137408 6 203 0 0% 0 0 0
jekyll (click) 1906730 1516323 336 3982 179 4% 0 0 0
lee (click) 349418 272373 44 562 67 11% 0 0 12
nbody (click) 173107 132369 8 149 0 0% 0 0 0
optcarrot (click) 501363 431426 196 3567 20 0% 0 0 0
rubykon (click) 307763 246251 138 1559 1 0% 0 0 0
30k_ifelse (click) 5552307 4345373 9261 57795 0 0% 0 0 0
30k_methods (click) 2173171 1655959 5780 19388 0 0% 0 0 0
cfunc_itself (click) 162291 124027 6 40 0 0% 0 0 0
fib (click) 160371 123419 6 29 0 0% 0 0 0
getivar (click) 162099 125930 6 56 0 0% 0 0 0
keyword_args (click) 163123 124668 7 42 0 0% 0 0 0
respond_to (click) 164403 125481 6 55 0 0% 0 0 0
setivar (click) 161843 124321 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.