YJIT Benchmarks

Details for Benchmarks at 2021-10-24 19:09:28

Overall YJIT is 30.6% faster than interpreted CRuby!
On Railsbench specifically, YJIT is 20.4% 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 124 10 120 10 177
hexapdf 10 10 10 10 10 10
liquid-render 10 102 10 110 10 148
mail 10 115 10 121 10 129
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 175 10 331 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 206 10 339 10 505
fib 10 92 10 307 10 375
getivar 10 212 10 211 10 529
keyword_args 10 75 10 98 10 432
respond_to 10 77 10 90 10 108
setivar 10 280 10 260 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) 1111578 865974 185 1162 0 0% 0 0 0
hexapdf (click) 1066036 892095 603 7827 619 7% 0 0 320
liquid-render (click) 461140 377135 143 1289 94 7% 0 0 1
mail (click) 1004186 777271 337 5215 131 2% 0 0 39
psych-load (click) 192234 155832 56 409 1 0% 0 0 0
railsbench (click) 2568433 2000902 1293 9596 262 2% 0 0 26
binarytrees (click) 113853 90204 9 49 0 0% 0 0 0
fannkuchredux (click) 129981 103829 6 203 0 0% 0 0 0
jekyll (click) 1962778 1631887 336 3762 173 4% 0 0 0
lee (click) 234666 181403 85 1091 114 10% 1 0 13
nbody (click) 123261 97934 8 149 0 0% 0 0 0
optcarrot (click) 459453 429726 196 3567 20 0% 0 0 0
30k_ifelse (click) 5561085 4890755 9261 57795 0 0% 0 0 0
30k_methods (click) 2117117 1816178 5780 19352 0 0% 0 0 0
cfunc_itself (click) 112381 88643 6 40 0 0% 0 0 0
fib (click) 110461 87838 6 29 0 0% 0 0 0
getivar (click) 112189 90811 6 56 0 0% 0 0 0
keyword_args (click) 112829 89021 7 42 0 0% 0 0 0
respond_to (click) 114173 89941 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.