YJIT Benchmarks

Details for Benchmarks at 2022-03-06 19:12:07

Overall YJIT is 32.0% faster than interpreted CRuby!
On Railsbench specifically, YJIT is 27.4% 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 MJIT warmups MJIT iters YJIT warmups YJIT iters
activerecord 5 180 75 180 20 180
hexapdf 5 15 20 15
liquid-render 5 156 75 156 20 156
mail 5 124 75 124 20 124
psych-load 5 15 75 15 20 15
railsbench 5 15 75 15 20 15
binarytrees 5 68 75 68 20 68
discourse 5 35 75 35 20 35
erubi 5 47 75 47 20 47
erubi_rails 5 965 75 965 20 965
fannkuchredux 5 15 75 15 20 15
lee 5 22 75 22 20 22
nbody 5 284 75 284 20 284
optcarrot 5 15 75 15 20 15
rubykon 5 15 37 15 20 15
30k_ifelse 5 55 75 55 20 55
30k_methods 5 22 29 22 20 22
cfunc_itself 5 451 75 451 20 451
fib 5 318 75 318 20 318
getivar 5 794 75 794 20 794
keyword_args 5 376 75 376 20 376
respond_to 5 103 75 103 20 103
setivar 5 1906 75 1906 20 1906

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) 990097 759432 185 1199 0 0% 0 0 0
hexapdf (click) 1112977 911939 599 8163 613 7% 0 0 320
liquid-render (click) 487953 387481 143 1561 95 6% 0 0 1
mail (click) 891153 668208 324 5458 125 2% 0 0 39
psych-load (click) 329617 260491 59 434 1 0% 0 0 0
railsbench (click) 2527569 1926843 1297 9298 268 2% 0 0 26
binarytrees (click) 151313 116018 11 59 0 0% 0 0 0
discourse (click) 23021009 11533484 3148 290428 266707 91% 2 0 133
erubi (click) 308625 242827 10 79 0 0% 0 0 0
erubi_rails (click) 1906129 1435385 262 1888 18 0% 0 0 3
fannkuchredux (click) 164561 126387 8 189 0 0% 0 0 0
lee (click) 371281 292325 45 587 69 11% 0 0 12
nbody (click) 160081 122890 10 159 0 0% 0 0 0
optcarrot (click) 478993 420805 198 3576 20 0% 0 0 0
rubykon (click) 296081 239243 140 1587 2 0% 0 0 0
30k_ifelse (click) 5539985 4336126 9263 57805 0 0% 0 0 0
30k_methods (click) 2154705 1643901 5782 19362 0 0% 0 0 0
cfunc_itself (click) 149265 114318 8 50 0 0% 0 0 0
fib (click) 147985 114039 8 39 0 0% 0 0 0
getivar (click) 141265 108722 8 66 0 0% 0 0 0
keyword_args (click) 150033 114861 9 52 0 0% 0 0 0
respond_to (click) 151249 115311 8 65 0 0% 0 0 0
setivar (click) 149393 114500 8 39 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.