YJIT Benchmarks

Details for Benchmarks at 2021-10-06 19:09:50

Overall YJIT is 23.8% faster than interpreted CRuby!
On Railsbench specifically, YJIT is 21.5% 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 120 10 169
hexapdf 10 10 10 10 10 10
liquid-render 10 106 10 112 10 127
mail 10 122 10 125 10 138
psych-load 10 10 10 10 10 10
railsbench 10 10 10 10 10 10
binarytrees 10 44 10 68 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 173 10 324 10 262
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 208 10 338 10 483
fib 10 89 10 308 10 375
getivar 10 228 10 211 10 530
keyword_args 10 76 10 96 10 75
respond_to 10 78 10 90 10 113
setivar 10 293 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) 1110618 863917 185 1151 0 0% 0 0 0
hexapdf (click) 975041 813668 603 7861 677 8% 0 0 320
liquid-render (click) 450452 367674 143 1203 94 7% 0 0 1
mail (click) 969498 749099 337 5007 129 2% 0 0 39
psych-load (click) 184938 148953 56 408 1 0% 0 0 0
railsbench (click) 2562673 1994155 1293 9555 262 2% 0 0 26
binarytrees (click) 112893 89319 9 49 0 0% 0 0 0
fannkuchredux (click) 128957 102944 6 203 0 0% 0 0 0
jekyll (click) 1953690 1624048 336 3732 173 4% 0 0 0
lee (click) 234026 180087 85 1086 114 10% 1 0 13
nbody (click) 122493 97197 8 149 0 0% 0 0 0
optcarrot (click) 649661 584204 286 5575 20 0% 0 0 0
30k_ifelse (click) 5560701 4890396 9261 57795 0 0% 0 0 0
30k_methods (click) 2117053 1816065 5780 19352 0 0% 0 0 0
cfunc_itself (click) 111357 87758 6 40 0 0% 0 0 0
fib (click) 109949 87479 6 29 0 0% 0 0 0
getivar (click) 111613 90172 6 56 0 0% 0 0 0
keyword_args (click) 109181 86511 7 22 0 0% 0 0 0
respond_to (click) 114173 89696 6 55 0 0% 0 0 0
setivar (click) 112125 88822 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.