YJIT Benchmarks

Details for Benchmarks at 2022-03-06 07:13:46

Overall YJIT is 32.8% faster than interpreted CRuby!
On Railsbench specifically, YJIT is 31.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 MJIT warmups MJIT iters YJIT warmups YJIT iters
activerecord 5 179 75 179 20 179
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 69 75 69 20 69
discourse 5 34 75 34 20 34
erubi 5 47 75 47 20 47
erubi_rails 5 982 75 982 20 982
fannkuchredux 5 15 75 15 20 15
lee 5 21 75 21 20 21
nbody 5 284 75 284 20 284
optcarrot 5 15 75 15 20 15
rubykon 5 15 38 15 20 15
30k_ifelse 5 56 75 56 20 56
30k_methods 5 22 29 22 20 22
cfunc_itself 5 451 75 451 20 451
fib 5 320 75 320 20 320
getivar 5 791 75 791 20 791
keyword_args 5 378 75 378 20 378
respond_to 5 102 75 102 20 102
setivar 5 1891 75 1891 20 1891

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 759345 185 1199 0 0% 0 0 0
hexapdf (click) 1114897 912887 600 8176 613 7% 0 0 320
liquid-render (click) 490257 389273 143 1550 95 6% 0 0 1
mail (click) 876689 656960 325 5312 124 2% 0 0 39
psych-load (click) 329489 260378 59 434 1 0% 0 0 0
railsbench (click) 2533009 1930292 1297 9341 268 2% 0 0 26
binarytrees (click) 150929 115802 11 59 0 0% 0 0 0
discourse (click) 22643921 11355813 3094 284913 261789 91% 2 0 133
erubi (click) 320977 254037 10 79 0 0% 0 0 0
erubi_rails (click) 1905489 1435162 262 1895 18 0% 0 0 3
fannkuchredux (click) 164561 126387 8 189 0 0% 0 0 0
lee (click) 372177 293203 45 587 69 11% 0 0 12
nbody (click) 160209 123003 10 159 0 0% 0 0 0
optcarrot (click) 487441 428633 198 3576 20 0% 0 0 0
rubykon (click) 292049 236129 140 1537 1 0% 0 0 0
30k_ifelse (click) 5539537 4335439 9263 57805 0 0% 0 0 0
30k_methods (click) 2155025 1644475 5782 19362 0 0% 0 0 0
cfunc_itself (click) 149393 114431 8 50 0 0% 0 0 0
fib (click) 147857 113926 8 39 0 0% 0 0 0
getivar (click) 149585 116437 8 66 0 0% 0 0 0
keyword_args (click) 150225 115047 9 52 0 0% 0 0 0
respond_to (click) 151569 115885 8 65 0 0% 0 0 0
setivar (click) 149585 114961 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.