YJIT Benchmarks

Details for Benchmarks at 2021-11-30 07:10:58

Overall YJIT is 28.7% faster than interpreted CRuby!
On Railsbench specifically, YJIT is 19.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 189 20 189 75 189 20 189
hexapdf 5 15 20 15 20 15
liquid-render 5 174 20 174 75 174 20 174
mail 5 135 20 135 75 135 20 135
psych-load 5 15 20 15 75 15 20 15
railsbench 5 15 20 15 75 15 20 15
binarytrees 5 86 20 86 75 86 20 86
erubi 5 51 20 51 75 51 20 51
erubi_rails 5 593 20 593 75 593 20 593
fannkuchredux 5 15 20 15 54 15 20 15
jekyll 5 15 20 15 36 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 44 15 20 15
30k_ifelse 5 64 20 64 74 64 20 64
30k_methods 5 26 20 26 40 26 20 26
cfunc_itself 5 497 20 497 75 497 20 497
fib 5 383 20 383 75 383 20 383
getivar 5 563 20 563 75 563 20 563
keyword_args 5 429 20 429 75 429 20 429
respond_to 5 127 20 127 75 127 20 127
setivar 5 511 20 511 75 511 20 511

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) 969834 729349 185 1176 0 0% 0 0 0
hexapdf (click) 1076010 857595 595 7992 615 7% 0 0 321
liquid-render (click) 465655 362201 143 1415 95 6% 0 0 1
mail (click) 865578 638841 325 5382 124 2% 0 0 39
psych-load (click) 290913 225811 57 423 1 0% 0 0 0
railsbench (click) 2574370 1921170 1293 9710 263 2% 0 0 26
binarytrees (click) 112293 85408 9 48 0 0% 0 0 0
erubi (click) 269281 208737 8 35 0 0% 0 0 0
erubi_rails (click) 2433954 1740085 260 1958 17 0% 0 0 3
fannkuchredux (click) 128805 97879 6 202 0 0% 0 0 0
jekyll (click) 1885162 1498595 336 3929 180 4% 0 0 0
lee (click) 330666 257206 44 562 67 11% 0 0 12
nbody (click) 122021 92707 8 148 0 0% 0 0 0
optcarrot (click) 450853 392113 196 3566 20 0% 0 0 0
rubykon (click) 253605 203672 138 1519 1 0% 0 0 0
30k_ifelse (click) 5501797 4306060 9261 57794 0 0% 0 0 0
30k_methods (click) 2116901 1614522 5780 19351 0 0% 0 0 0
cfunc_itself (click) 111205 84365 6 39 0 0% 0 0 0
fib (click) 109349 83645 6 28 0 0% 0 0 0
getivar (click) 111077 86156 6 55 0 0% 0 0 0
keyword_args (click) 112037 85006 7 41 0 0% 0 0 0
respond_to (click) 113509 85952 6 54 0 0% 0 0 0
setivar (click) 111333 85008 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.