YJIT Benchmarks

Details for Benchmarks at 2021-10-19 07:09:54

Overall YJIT is 27.2% faster than interpreted CRuby!
On Railsbench specifically, YJIT is 18.9% 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 126 10 121 10 172
hexapdf 10 10 10 10 10 10
liquid-render 10 106 10 113 10 150
mail 10 118 10 125 10 132
psych-load 10 10 10 10 10 10
railsbench 10 10 10 10 10 10
binarytrees 10 45 10 69 10 60
fannkuchredux 10 10 10 10 10 10
jekyll 10 10 10 10 10 10
lee 10 10 10 13 10 15
nbody 10 173 10 297 10 256
optcarrot 10 10 10 10 10 10
30k_ifelse 10 10 10 10 10 50
30k_methods 10 10 10 10 10 17
cfunc_itself 10 209 10 336 10 491
fib 10 95 10 307 10 374
getivar 10 230 10 211 10 530
keyword_args 10 76 10 98 10 424
respond_to 10 75 10 90 10 109
setivar 10 284 10 265 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) 1110810 865446 185 1153 0 0% 0 0 0
hexapdf (click) 1065076 891245 603 7814 619 7% 0 0 320
liquid-render (click) 462228 377697 143 1316 94 7% 0 0 1
mail (click) 997402 771056 337 5195 129 2% 0 0 39
psych-load (click) 185002 149311 56 409 1 0% 0 0 0
railsbench (click) 2555697 1992878 1293 9495 262 2% 0 0 26
binarytrees (click) 113853 90204 9 49 0 0% 0 0 0
fannkuchredux (click) 129917 103829 6 203 0 0% 0 0 0
jekyll (click) 1961754 1631913 336 3730 173 4% 0 0 0
lee (click) 234858 181419 85 1091 114 10% 1 0 13
nbody (click) 123261 97934 8 149 0 0% 0 0 0
optcarrot (click) 458877 429332 196 3567 20 0% 0 0 0
30k_ifelse (click) 5561149 4890755 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) 110781 88216 6 29 0 0% 0 0 0
getivar (click) 112637 91057 6 56 0 0% 0 0 0
keyword_args (click) 112765 89153 7 42 0 0% 0 0 0
respond_to (click) 114557 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.