YJIT Benchmarks

Details for Benchmarks at 2021-10-25 07:09:56

Overall YJIT is 28.9% faster than interpreted CRuby!
On Railsbench specifically, YJIT is 20.1% 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 122 10 172
hexapdf 10 10 10 10 10 10
liquid-render 10 102 10 110 10 149
mail 10 117 10 120 10 134
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 15
nbody 10 176 10 331 10 256
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 205 10 338 10 504
fib 10 92 10 306 10 375
getivar 10 212 10 211 10 528
keyword_args 10 74 10 96 10 429
respond_to 10 77 10 89 10 109
setivar 10 287 10 265 10 460

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) 1111962 866396 185 1158 0 0% 0 0 0
hexapdf (click) 1066036 892095 603 7827 619 7% 0 0 320
liquid-render (click) 458132 375059 143 1245 95 7% 0 0 1
mail (click) 1000922 774586 337 5194 129 2% 0 0 39
psych-load (click) 192234 155832 56 409 1 0% 0 0 0
railsbench (click) 2568177 2000466 1293 9603 262 2% 0 0 26
binarytrees (click) 113533 89826 9 49 0 0% 0 0 0
fannkuchredux (click) 129917 103829 6 203 0 0% 0 0 0
jekyll (click) 1956698 1627626 336 3723 173 4% 0 0 0
lee (click) 234538 181173 85 1091 114 10% 1 0 13
nbody (click) 122877 97688 8 149 0 0% 0 0 0
optcarrot (click) 459453 429726 196 3567 20 0% 0 0 0
30k_ifelse (click) 5561533 4891133 9261 57795 0 0% 0 0 0
30k_methods (click) 2117693 1816572 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) 111677 90285 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) 112125 89120 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.