YJIT Benchmarks

Details for Benchmarks at 2021-11-10 07:11:49

Overall YJIT is 28.9% faster than interpreted CRuby!
On Railsbench specifically, YJIT is 15.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 125 10 117 10 179
hexapdf 10 10 10 10 10 10
liquid-render 10 105 10 114 10 164
mail 10 116 10 122 10 131
psych-load 10 10 10 10 10 10
railsbench 10 10 10 10 10 10
binarytrees 10 46 10 70 10 61
fannkuchredux 10 10 10 10 10 10
jekyll 10 10 10 10 10 10
lee 10 10 10 14 10 15
nbody 10 171 10 331 10 257
optcarrot 10 10 10 10 10 10
rubykon 10 10 10 10 10 10
30k_ifelse 10 10 10 10 10 54
30k_methods 10 10 10 10 10 17
cfunc_itself 10 214 10 331 10 499
fib 10 94 10 308 10 373
getivar 10 220 10 208 10 541
keyword_args 10 77 10 97 10 429
respond_to 10 76 10 90 10 118
setivar 10 278 10 264 10 500

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) 971114 679616 184 1180 0 0% 0 0 0
hexapdf (click) 1087210 812593 604 8068 647 8% 0 0 320
liquid-render (click) 467255 340954 143 1424 95 6% 0 0 1
mail (click) 857962 589873 339 5254 124 2% 0 0 39
psych-load (click) 298081 212106 57 435 1 0% 0 0 0
railsbench (click) 2592098 1801508 1295 9727 263 2% 0 0 26
binarytrees (click) 113701 80936 9 48 0 0% 0 0 0
fannkuchredux (click) 129253 92618 6 202 0 0% 0 0 0
jekyll (click) 1889002 1394270 336 3926 179 4% 0 0 0
lee (click) 345194 239820 44 566 70 12% 0 0 12
nbody (click) 122725 87443 8 148 0 0% 0 0 0
optcarrot (click) 451621 381143 196 3566 20 0% 0 0 0
rubykon (click) 255333 197194 139 1529 2 0% 0 0 0
30k_ifelse (click) 5502501 4300932 9261 57794 0 0% 0 0 0
30k_methods (click) 2117605 1609394 5780 19351 0 0% 0 0 0
cfunc_itself (click) 111909 79237 6 39 0 0% 0 0 0
fib (click) 110373 78845 6 28 0 0% 0 0 0
getivar (click) 112101 81356 6 55 0 0% 0 0 0
keyword_args (click) 112357 79662 7 41 0 0% 0 0 0
respond_to (click) 113765 80550 6 54 0 0% 0 0 0
setivar (click) 112037 79880 6 28 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.