YJIT Benchmarks

Details for Benchmarks at 2021-12-25 19:15:44

Overall YJIT is 25.4% faster than interpreted CRuby!
On Railsbench specifically, YJIT is 23.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 MJIT warmups MJIT iters YJIT warmups YJIT iters
activerecord 5 190 20 190 75 190 20 190
hexapdf 5 15 20 15 20 15
liquid-render 5 158 20 158 75 158 20 158
mail 5 138 20 138 75 138 20 138
psych-load 5 15 20 15 75 15 20 15
railsbench 5 15 20 15 75 15 20 15
binarytrees 5 85 20 85 75 85 20 85
erubi 5 53 20 53 75 53 20 53
erubi_rails 5 627 20 627 75 627 20 627
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 342 20 342 75 342 20 342
optcarrot 5 15 20 15 75 15 20 15
rubykon 5 15 20 15 43 15 20 15
30k_ifelse 5 64 20 64 73 64 20 64
30k_methods 5 27 20 27 44 27 20 27
cfunc_itself 5 509 20 509 75 509 20 509
fib 5 383 20 383 75 383 20 383
getivar 5 563 20 563 75 563 20 563
keyword_args 5 436 20 436 75 436 20 436
respond_to 5 126 20 126 75 126 20 126
setivar 5 477 20 477 75 477 20 477

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) 979306 747001 185 1194 0 0% 0 0 0
hexapdf (click) 1122474 916969 599 8110 620 7% 0 0 321
liquid-render (click) 470263 371791 143 1435 95 6% 0 0 1
mail (click) 864618 643052 325 5388 124 2% 0 0 39
psych-load (click) 299041 235642 57 423 1 0% 0 0 0
railsbench (click) 2515874 1901936 1295 9282 266 2% 0 0 26
binarytrees (click) 113061 86697 9 48 0 0% 0 0 0
erubi (click) 278497 219067 8 35 0 0% 0 0 0
erubi_rails (click) 2484962 1791997 261 1973 17 0% 0 0 3
fannkuchredux (click) 128933 98594 6 202 0 0% 0 0 0
jekyll (click) 1849322 1486912 338 3734 185 4% 0 0 0
lee (click) 337121 265463 43 557 70 12% 0 0 12
nbody (click) 122341 93785 8 148 0 0% 0 0 0
optcarrot (click) 452069 399926 196 3566 20 0% 0 0 0
rubykon (click) 254885 207268 139 1527 1 0% 0 0 0
30k_ifelse (click) 5502565 4307237 9261 57794 0 0% 0 0 0
30k_methods (click) 2117349 1615483 5780 19351 0 0% 0 0 0
cfunc_itself (click) 112037 85542 6 39 0 0% 0 0 0
fib (click) 109989 84821 6 28 0 0% 0 0 0
getivar (click) 111717 87332 6 55 0 0% 0 0 0
keyword_args (click) 112357 85854 7 41 0 0% 0 0 0
respond_to (click) 113765 86780 6 54 0 0% 0 0 0
setivar (click) 111653 85856 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.