YJIT Benchmarks

Details for Benchmarks at 2021-12-05 19:10:13

Overall YJIT is 31.2% faster than interpreted CRuby!
On Railsbench specifically, YJIT is 28.7% 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 189 20 189 75 189 20 189
hexapdf 5 15 20 15 20 15
liquid-render 5 167 20 167 75 167 20 167
mail 5 139 20 139 75 139 20 139
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 52 20 52 75 52 20 52
erubi_rails 5 602 20 602 75 602 20 602
fannkuchredux 5 15 20 15 53 15 20 15
jekyll 5 15 20 15 35 15 20 15
lee 5 26 20 26 75 26 20 26
nbody 5 341 20 341 75 341 20 341
optcarrot 5 15 20 15 75 15 20 15
rubykon 5 15 20 15 43 15 20 15
30k_ifelse 5 64 20 64 70 64 20 64
30k_methods 5 26 20 26 44 26 20 26
cfunc_itself 5 485 20 485 75 485 20 485
fib 5 382 20 382 75 382 20 382
getivar 5 499 20 499 75 499 20 499
keyword_args 5 435 20 435 75 435 20 435
respond_to 5 128 20 128 75 128 20 128
setivar 5 480 20 480 75 480 20 480

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) 990378 758722 185 1194 0 0% 0 0 0
hexapdf (click) 1095722 898103 595 7994 616 7% 0 0 321
liquid-render (click) 490053 389193 143 1422 95 6% 0 0 1
mail (click) 895402 668987 325 5453 124 2% 0 0 39
psych-load (click) 312481 247715 57 436 1 0% 0 0 0
railsbench (click) 2523618 1917363 1295 9291 263 2% 0 0 26
binarytrees (click) 163379 127377 9 49 0 0% 0 0 0
erubi (click) 291041 230499 8 35 0 0% 0 0 0
erubi_rails (click) 2404642 1749852 260 1969 16 0% 0 0 3
fannkuchredux (click) 179443 139387 6 203 0 0% 0 0 0
jekyll (click) 1876586 1517994 337 3764 186 4% 0 0 0
lee (click) 350122 277047 44 562 67 11% 0 0 12
nbody (click) 173043 134749 8 149 0 0% 0 0 0
optcarrot (click) 502259 449943 196 3567 20 0% 0 0 0
rubykon (click) 304435 249170 138 1519 1 0% 0 0 0
30k_ifelse (click) 5553203 4368110 9261 57795 0 0% 0 0 0
30k_methods (click) 2168307 1656532 5780 19352 0 0% 0 0 0
cfunc_itself (click) 162035 126006 6 40 0 0% 0 0 0
fib (click) 160499 125614 6 29 0 0% 0 0 0
getivar (click) 162227 128325 6 56 0 0% 0 0 0
keyword_args (click) 162547 126299 7 42 0 0% 0 0 0
respond_to (click) 164147 127460 6 55 0 0% 0 0 0
setivar (click) 162355 126782 6 29 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.