YJIT Benchmarks

Details for Benchmarks at 2021-10-24 07:09:40

Overall YJIT is 26.1% faster than interpreted CRuby!
On Railsbench specifically, YJIT is 18.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 YJIT warmups YJIT iters
activerecord 10 129 10 121 10 171
hexapdf 10 10 10 10 10 10
liquid-render 10 103 10 114 10 145
mail 10 119 10 122 10 131
psych-load 10 10 10 10 10 10
railsbench 10 10 10 10 10 10
binarytrees 10 44 10 69 10 57
fannkuchredux 10 10 10 10 10 10
jekyll 10 10 10 10 10 10
lee 10 10 10 13 10 16
nbody 10 172 10 324 10 256
optcarrot 10 10 10 10 10 10
30k_ifelse 10 10 10 10 10 52
30k_methods 10 10 10 10 10 17
cfunc_itself 10 203 10 339 10 504
fib 10 92 10 306 10 375
getivar 10 212 10 211 10 529
keyword_args 10 74 10 98 10 432
respond_to 10 78 10 89 10 110
setivar 10 269 10 265 10 460

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) 1109722 864712 185 1147 0 0% 0 0 0
hexapdf (click) 1066420 892493 604 7831 619 7% 0 0 320
liquid-render (click) 458260 375277 143 1252 94 7% 0 0 1
mail (click) 984858 762014 337 5028 131 2% 0 0 39
psych-load (click) 192234 155832 56 409 1 0% 0 0 0
railsbench (click) 2568561 2000875 1293 9604 262 2% 0 0 26
binarytrees (click) 113533 89826 9 49 0 0% 0 0 0
fannkuchredux (click) 129341 103435 6 203 0 0% 0 0 0
jekyll (click) 1966298 1634090 336 3790 173 4% 0 0 0
lee (click) 234794 181551 85 1091 114 10% 1 0 13
nbody (click) 123261 97934 8 149 0 0% 0 0 0
optcarrot (click) 459837 430104 196 3567 20 0% 0 0 0
30k_ifelse (click) 5561149 4890755 9261 57795 0 0% 0 0 0
30k_methods (click) 2118077 1816950 5780 19352 0 0% 0 0 0
cfunc_itself (click) 111997 88265 6 40 0 0% 0 0 0
fib (click) 110397 87970 6 29 0 0% 0 0 0
getivar (click) 111677 90285 6 56 0 0% 0 0 0
keyword_args (click) 112829 89021 7 42 0 0% 0 0 0
respond_to (click) 114621 90187 6 55 0 0% 0 0 0
setivar (click) 112189 89120 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.