YJIT Benchmarks

Details for Benchmarks at 2021-10-08 07:10:24

Overall YJIT is 24.2% faster than interpreted CRuby!
On Railsbench specifically, YJIT is 23.6% 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 127 10 118 10 175
hexapdf 10 10 10 10 10 10
liquid-render 10 107 10 112 10 129
mail 10 123 10 124 10 136
psych-load 10 10 10 10 10 10
railsbench 10 10 10 10 10 10
binarytrees 10 44 10 69 10 59
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 325 10 264
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 217 10 334 10 499
fib 10 94 10 307 10 375
getivar 10 229 10 212 10 530
keyword_args 10 76 10 97 10 74
respond_to 10 78 10 90 10 112
setivar 10 292 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) 1108442 862540 185 1143 0 0% 0 0 0
hexapdf (click) 974209 812811 603 7856 677 8% 0 0 320
liquid-render (click) 453780 370011 143 1228 94 7% 0 0 1
mail (click) 971162 749957 337 5016 129 2% 0 0 39
psych-load (click) 184554 148707 56 408 1 0% 0 0 0
railsbench (click) 2562801 1994843 1293 9554 262 2% 0 0 26
binarytrees (click) 113469 89713 9 49 0 0% 0 0 0
fannkuchredux (click) 129469 103338 6 203 0 0% 0 0 0
jekyll (click) 1955162 1625469 336 3732 173 4% 0 0 0
lee (click) 234602 180481 85 1083 114 10% 1 0 13
nbody (click) 122493 97197 8 149 0 0% 0 0 0
optcarrot (click) 649085 583810 286 5575 20 0% 0 0 0
30k_ifelse (click) 5560637 4890396 9261 57795 0 0% 0 0 0
30k_methods (click) 2117565 1816406 5780 19352 0 0% 0 0 0
cfunc_itself (click) 111549 87906 6 40 0 0% 0 0 0
fib (click) 110013 87479 6 29 0 0% 0 0 0
getivar (click) 111805 90320 6 56 0 0% 0 0 0
keyword_args (click) 109309 86659 7 22 0 0% 0 0 0
respond_to (click) 114173 89696 6 55 0 0% 0 0 0
setivar (click) 112189 88875 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.