YJIT Benchmarks

Details for Benchmarks at 2021-12-07 19:11:51

Overall YJIT is 31.9% faster than interpreted CRuby!
On Railsbench specifically, YJIT is 28.5% 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 171 20 171 75 171 20 171
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 88 20 88 75 88 20 88
erubi 5 51 20 51 75 51 20 51
erubi_rails 5 610 20 610 75 610 20 610
fannkuchredux 5 15 20 15 51 15 20 15
jekyll 5 15 20 15 35 15 20 15
lee 5 26 20 26 75 26 20 26
nbody 5 336 20 336 75 336 20 336
optcarrot 5 15 20 15 75 15 20 15
rubykon 5 15 20 15 44 15 20 15
30k_ifelse 5 62 20 62 70 62 20 62
30k_methods 5 26 20 26 44 26 20 26
cfunc_itself 5 506 20 506 75 506 20 506
fib 5 383 20 383 75 383 20 383
getivar 5 562 20 562 75 562 20 562
keyword_args 5 432 20 432 75 432 20 432
respond_to 5 131 20 131 75 131 20 131
setivar 5 500 20 500 75 500 20 500

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) 989994 758275 185 1194 0 0% 0 0 0
hexapdf (click) 1094122 896121 596 7983 614 7% 0 0 321
liquid-render (click) 492293 390813 143 1444 95 6% 0 0 1
mail (click) 891690 666673 325 5432 124 2% 0 0 39
psych-load (click) 312417 247225 57 435 1 0% 0 0 0
railsbench (click) 2519202 1914016 1295 9258 263 2% 0 0 26
binarytrees (click) 163507 127265 9 49 0 0% 0 0 0
erubi (click) 289825 229351 8 35 0 0% 0 0 0
erubi_rails (click) 2408226 1752951 260 1939 16 0% 0 0 3
fannkuchredux (click) 179507 139275 6 203 0 0% 0 0 0
jekyll (click) 1872170 1514370 336 3725 185 4% 0 0 0
lee (click) 349610 276586 44 562 67 11% 0 0 12
nbody (click) 172915 134636 8 149 0 0% 0 0 0
optcarrot (click) 501747 449482 196 3567 20 0% 0 0 0
rubykon (click) 305203 249703 138 1528 1 0% 0 0 0
30k_ifelse (click) 5552691 4367689 9261 57795 0 0% 0 0 0
30k_methods (click) 2172083 1657878 5780 19378 0 0% 0 0 0
cfunc_itself (click) 162099 125894 6 40 0 0% 0 0 0
fib (click) 160755 125675 6 29 0 0% 0 0 0
getivar (click) 162483 128386 6 56 0 0% 0 0 0
keyword_args (click) 162931 126535 7 42 0 0% 0 0 0
respond_to (click) 164211 127348 6 55 0 0% 0 0 0
setivar (click) 162227 126537 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.