YJIT Benchmarks

Details for Benchmarks at 2021-10-23 07:09:54

Overall YJIT is 25.2% faster than interpreted CRuby!
On Railsbench specifically, YJIT is 18.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 127 10 118 10 176
hexapdf 10 10 10 10 10 10
liquid-render 10 102 10 109 10 145
mail 10 119 10 120 10 130
psych-load 10 10 10 10 10 10
railsbench 10 10 10 10 10 10
binarytrees 10 44 10 68 10 57
fannkuchredux 10 10 10 10 10 10
jekyll 10 10 10 10 10 10
lee 10 10 10 13 10 16
nbody 10 176 10 331 10 255
optcarrot 10 10 10 10 10 10
30k_ifelse 10 10 10 10 10 52
30k_methods 10 10 10 10 10 17
cfunc_itself 10 204 10 337 10 504
fib 10 85 10 307 10 375
getivar 10 212 10 210 10 528
keyword_args 10 75 10 96 10 411
respond_to 10 78 10 89 10 110
setivar 10 272 10 262 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) 1111066 865696 185 1149 0 0% 0 0 0
hexapdf (click) 1066804 892841 603 7830 621 7% 0 0 320
liquid-render (click) 456468 373454 143 1270 94 7% 0 0 1
mail (click) 1000730 774700 337 5196 129 2% 0 0 39
psych-load (click) 184490 148785 56 409 1 0% 0 0 0
railsbench (click) 2567729 1999839 1293 9600 262 2% 0 0 26
binarytrees (click) 113853 90204 9 49 0 0% 0 0 0
fannkuchredux (click) 129917 103829 6 203 0 0% 0 0 0
jekyll (click) 1960730 1630708 336 3728 173 4% 0 0 0
lee (click) 234922 181419 85 1091 114 10% 1 0 13
nbody (click) 123325 97934 8 149 0 0% 0 0 0
optcarrot (click) 459453 429726 196 3567 20 0% 0 0 0
30k_ifelse (click) 5561149 4890755 9261 57795 0 0% 0 0 0
30k_methods (click) 2118013 1816950 5780 19352 0 0% 0 0 0
cfunc_itself (click) 112317 88643 6 40 0 0% 0 0 0
fib (click) 110845 88216 6 29 0 0% 0 0 0
getivar (click) 112253 90679 6 56 0 0% 0 0 0
keyword_args (click) 112253 88627 7 42 0 0% 0 0 0
respond_to (click) 114557 90187 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.