YJIT Benchmarks

Details for Benchmarks at 2021-10-28 07:09:53

Overall YJIT is 27.7% faster than interpreted CRuby!
On Railsbench specifically, YJIT is 21.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 YJIT warmups YJIT iters
activerecord 10 131 10 118 10 178
hexapdf 10 10 10 10 10 10
liquid-render 10 106 10 112 10 149
mail 10 117 10 123 10 132
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 175 10 332 10 256
optcarrot 10 10 10 10 10 10
rubykon 10 10 10 10 10 10
30k_ifelse 10 10 10 10 10 51
30k_methods 10 10 10 10 10 17
cfunc_itself 10 206 10 339 10 489
fib 10 93 10 308 10 375
getivar 10 207 10 211 10 529
keyword_args 10 74 10 97 10 424
respond_to 10 76 10 89 10 112
setivar 10 287 10 265 10 457

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) 1117466 871090 185 1160 0 0% 0 0 0
hexapdf (click) 1073396 897939 603 7827 621 7% 0 0 320
liquid-render (click) 461185 377223 143 1285 94 7% 0 0 1
mail (click) 850996 659595 339 5190 124 2% 0 0 39
psych-load (click) 192874 156132 56 409 1 0% 0 0 0
railsbench (click) 2581361 2015979 1293 9540 262 2% 0 0 26
binarytrees (click) 114218 90617 9 48 0 0% 0 0 0
fannkuchredux (click) 130474 104390 6 202 0 0% 0 0 0
jekyll (click) 1961050 1631030 336 3735 173 4% 0 0 0
lee (click) 235498 181947 85 1082 114 10% 1 0 13
nbody (click) 124202 98741 8 148 0 0% 0 0 0
optcarrot (click) 460714 430911 196 3566 20 0% 0 0 0
rubykon (click) 255722 221001 138 1501 2 0% 0 0 0
30k_ifelse (click) 5562474 4891940 9261 57794 0 0% 0 0 0
30k_methods (click) 2118634 1817379 5780 19351 0 0% 0 0 0
cfunc_itself (click) 112938 89072 6 39 0 0% 0 0 0
fib (click) 110826 88251 6 28 0 0% 0 0 0
getivar (click) 112938 91470 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) 113130 89927 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.