YJIT Benchmarks

Details for Benchmarks at 2021-10-29 07:09:55

Overall YJIT is 28.1% faster than interpreted CRuby!
On Railsbench specifically, YJIT is 25.0% 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 YJIT warmups YJIT iters
activerecord 10 129 10 115 10 173
hexapdf 10 10 10 10 10 10
liquid-render 10 102 10 106 10 144
mail 10 116 10 119 10 130
psych-load 10 10 10 10 10 10
railsbench 10 10 10 10 10 10
binarytrees 10 44 10 69 10 57
fannkuchredux 10 10 10 10 10 10
jekyll 10 10 10 10 10 10
lee 10 10 10 13 10 16
nbody 10 176 10 331 10 256
optcarrot 10 10 10 10 10 10
rubykon 10 10 10 10 10 10
30k_ifelse 10 10 10 10 10 52
30k_methods 10 10 10 10 10 17
cfunc_itself 10 205 10 336 10 508
fib 10 94 10 307 10 375
getivar 10 210 10 211 10 527
keyword_args 10 75 10 97 10 432
respond_to 10 76 10 90 10 112
setivar 10 276 10 265 10 459

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) 1116442 870563 185 1156 0 0% 0 0 0
hexapdf (click) 1078388 903351 603 7829 619 7% 0 0 320
liquid-render (click) 459905 376225 143 1285 94 7% 0 0 1
mail (click) 853876 661359 339 5217 124 2% 0 0 39
psych-load (click) 192810 156264 56 409 1 0% 0 0 0
railsbench (click) 2578225 2013928 1293 9519 262 2% 0 0 26
binarytrees (click) 114218 90617 9 48 0 0% 0 0 0
fannkuchredux (click) 130858 104636 6 202 0 0% 0 0 0
jekyll (click) 1962138 1631214 336 3755 172 4% 0 0 0
lee (click) 235370 181947 85 1082 114 10% 1 0 13
nbody (click) 123818 98495 8 148 0 0% 0 0 0
optcarrot (click) 460650 430911 196 3566 20 0% 0 0 0
rubykon (click) 256490 221652 138 1507 1 0% 0 0 0
30k_ifelse (click) 5562090 4891562 9261 57794 0 0% 0 0 0
30k_methods (click) 2118954 1817757 5780 19351 0 0% 0 0 0
cfunc_itself (click) 113322 89450 6 39 0 0% 0 0 0
fib (click) 111402 88645 6 28 0 0% 0 0 0
getivar (click) 113578 91864 6 55 0 0% 0 0 0
keyword_args (click) 113770 89828 7 41 0 0% 0 0 0
respond_to (click) 115498 90994 6 54 0 0% 0 0 0
setivar (click) 113514 90173 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.