YJIT Benchmarks

Details for Benchmarks at 2021-10-11 19:09:27

Overall YJIT is 27.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 131 10 120 10 175
hexapdf 10 10 10 10 10 10
liquid-render 10 104 10 112 10 149
mail 10 117 10 125 10 131
psych-load 10 10 10 10 10 10
railsbench 10 10 10 10 10 10
binarytrees 10 44 10 68 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 172 10 332 10 256
optcarrot 10 10 10 10 10 10
30k_ifelse 10 10 10 10 10 51
30k_methods 10 10 10 10 10 17
cfunc_itself 10 210 10 335 10 508
fib 10 94 10 308 10 375
getivar 10 212 10 211 10 528
keyword_args 10 76 10 95 10 429
respond_to 10 76 10 90 10 108
setivar 10 283 10 265 10 519

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) 1114074 867938 185 1167 0 0% 0 0 0
hexapdf (click) 975873 816669 602 7881 675 8% 0 0 320
liquid-render (click) 458068 374552 143 1281 94 7% 0 0 1
mail (click) 988122 763689 337 5188 129 2% 0 0 39
psych-load (click) 184938 149311 56 409 1 0% 0 0 0
railsbench (click) 2565489 1999237 1293 9589 262 2% 0 0 26
binarytrees (click) 113469 89826 9 49 0 0% 0 0 0
fannkuchredux (click) 129853 103829 6 203 0 0% 0 0 0
jekyll (click) 1959834 1630146 336 3741 173 4% 0 0 0
lee (click) 235242 181797 85 1091 114 10% 1 0 13
nbody (click) 123261 97934 8 149 0 0% 0 0 0
optcarrot (click) 650109 584808 286 5576 20 0% 0 0 0
30k_ifelse (click) 5560573 4890361 9261 57795 0 0% 0 0 0
30k_methods (click) 2117629 1816572 5780 19352 0 0% 0 0 0
cfunc_itself (click) 111997 88265 6 40 0 0% 0 0 0
fib (click) 110845 88216 6 29 0 0% 0 0 0
getivar (click) 112573 91057 6 56 0 0% 0 0 0
keyword_args (click) 112829 89021 7 42 0 0% 0 0 0
respond_to (click) 114237 89809 6 55 0 0% 0 0 0
setivar (click) 112189 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.