YJIT Benchmarks

Details for Benchmarks at 2021-10-13 07:09:47

Overall YJIT is 27.5% faster than interpreted CRuby!
On Railsbench specifically, YJIT is 19.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 128 10 121 10 179
hexapdf 10 10 10 10 10 10
liquid-render 10 105 10 113 10 150
mail 10 119 10 123 10 132
psych-load 10 10 10 10 10 10
railsbench 10 10 10 10 10 10
binarytrees 10 44 10 69 10 60
fannkuchredux 10 10 10 10 10 10
jekyll 10 10 10 10 10 10
lee 10 10 10 13 10 16
nbody 10 174 10 331 10 255
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 216 10 339 10 500
fib 10 94 10 308 10 375
getivar 10 220 10 211 10 530
keyword_args 10 75 10 98 10 426
respond_to 10 77 10 90 10 112
setivar 10 273 10 264 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) 1114010 867819 185 1165 0 0% 0 0 0
hexapdf (click) 975553 816566 602 7876 677 8% 0 0 320
liquid-render (click) 456276 373431 143 1263 94 7% 0 0 1
mail (click) 992410 766826 337 5214 129 2% 0 0 39
psych-load (click) 185002 149179 56 409 1 0% 0 0 0
railsbench (click) 2566513 1999576 1293 9587 262 2% 0 0 26
binarytrees (click) 112957 89432 9 49 0 0% 0 0 0
fannkuchredux (click) 129597 103451 6 203 0 0% 0 0 0
jekyll (click) 1963354 1632021 336 3739 173 4% 0 0 0
lee (click) 234922 181419 85 1091 114 10% 1 0 13
nbody (click) 122941 97556 8 149 0 0% 0 0 0
optcarrot (click) 459453 429726 196 3567 20 0% 0 0 0
30k_ifelse (click) 5561085 4890755 9261 57795 0 0% 0 0 0
30k_methods (click) 2118013 1816950 5780 19352 0 0% 0 0 0
cfunc_itself (click) 112381 88643 6 40 0 0% 0 0 0
fib (click) 110461 87838 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) 114173 89941 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.