YJIT Benchmarks

Details for Benchmarks at 2021-10-12 19:09:32

Overall YJIT is 26.1% faster than interpreted CRuby!
On Railsbench specifically, YJIT is 20.3% 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 128 10 122 10 179
hexapdf 10 10 10 10 10 10
liquid-render 10 103 10 114 10 151
mail 10 119 10 117 10 132
psych-load 10 10 10 10 10 10
railsbench 10 10 10 10 10 10
binarytrees 10 44 10 66 10 58
fannkuchredux 10 10 10 10 10 10
jekyll 10 10 10 10 10 10
lee 10 10 10 13 10 16
nbody 10 174 10 332 10 255
optcarrot 10 10 10 10 10 10
30k_ifelse 10 10 10 10 10 53
30k_methods 10 10 10 10 10 17
cfunc_itself 10 216 10 335 10 501
fib 10 94 10 308 10 375
getivar 10 219 10 212 10 530
keyword_args 10 75 10 98 10 410
respond_to 10 77 10 90 10 112
setivar 10 273 10 263 10 458

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) 1114202 867591 185 1166 0 0% 0 0 0
hexapdf (click) 976321 817150 603 7880 675 8% 0 0 320
liquid-render (click) 458452 374705 143 1285 94 7% 0 0 1
mail (click) 989658 764763 337 5199 129 2% 0 0 39
psych-load (click) 185450 149557 56 409 1 0% 0 0 0
railsbench (click) 2566961 2001101 1293 9596 262 2% 0 0 26
binarytrees (click) 112957 89432 9 49 0 0% 0 0 0
fannkuchredux (click) 129597 103451 6 203 0 0% 0 0 0
jekyll (click) 1966810 1634635 336 3778 173 4% 0 0 0
lee (click) 235178 181797 85 1091 114 10% 1 0 13
nbody (click) 123325 97934 8 149 0 0% 0 0 0
optcarrot (click) 459837 430104 196 3567 20 0% 0 0 0
30k_ifelse (click) 5561533 4891133 9261 57795 0 0% 0 0 0
30k_methods (click) 2117693 1816572 5780 19352 0 0% 0 0 0
cfunc_itself (click) 111997 88265 6 40 0 0% 0 0 0
fib (click) 110461 87838 6 29 0 0% 0 0 0
getivar (click) 112253 90679 6 56 0 0% 0 0 0
keyword_args (click) 112253 88627 7 42 0 0% 0 0 0
respond_to (click) 114685 90187 6 55 0 0% 0 0 0
setivar (click) 112253 88988 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.