YJIT Benchmarks

Details for Benchmarks at 2021-12-12 07:10:39

Overall YJIT is 31.6% faster than interpreted CRuby!
On Railsbench specifically, YJIT is 27.0% 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 MJIT warmups MJIT iters YJIT warmups YJIT iters
activerecord 5 185 20 185 75 185 20 185
hexapdf 5 15 20 15 20 15
liquid-render 5 173 20 173 75 173 20 173
mail 5 140 20 140 75 140 20 140
psych-load 5 15 20 15 75 15 20 15
railsbench 5 15 20 15 75 15 20 15
binarytrees 5 87 20 87 75 87 20 87
erubi 5 51 20 51 75 51 20 51
erubi_rails 5 601 20 601 75 601 20 601
fannkuchredux 5 15 20 15 52 15 20 15
jekyll 5 15 20 15 36 15 20 15
lee 5 27 20 27 75 27 20 27
nbody 5 343 20 343 75 343 20 343
optcarrot 5 15 20 15 75 15 20 15
rubykon 5 15 20 15 43 15 20 15
30k_ifelse 5 65 20 65 75 65 20 65
30k_methods 5 26 20 26 41 26 20 26
cfunc_itself 5 500 20 500 75 500 20 500
fib 5 383 20 383 75 383 20 383
getivar 5 563 20 563 75 563 20 563
keyword_args 5 437 20 437 75 437 20 437
respond_to 5 132 20 132 75 132 20 132
setivar 5 506 20 506 75 506 20 506

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) 990122 756996 185 1194 0 0% 0 0 0
hexapdf (click) 1096362 893407 595 8001 614 7% 0 0 321
liquid-render (click) 494981 390941 143 1466 95 6% 0 0 1
mail (click) 873066 652345 325 5228 124 2% 0 0 39
psych-load (click) 311905 246350 57 428 1 0% 0 0 0
railsbench (click) 2516066 1907805 1295 9261 263 2% 0 0 26
binarytrees (click) 164531 127410 9 49 0 0% 0 0 0
erubi (click) 290849 229356 8 35 0 0% 0 0 0
erubi_rails (click) 2491490 1801345 261 2022 17 0% 0 0 3
fannkuchredux (click) 180531 139420 6 203 0 0% 0 0 0
jekyll (click) 1880618 1513170 336 3753 184 4% 0 0 0
lee (click) 348961 275343 43 557 66 11% 0 0 12
nbody (click) 173939 134611 8 149 0 0% 0 0 0
optcarrot (click) 502771 440147 196 3567 20 0% 0 0 0
rubykon (click) 305395 247096 138 1521 1 0% 0 0 0
30k_ifelse (click) 5553651 4347734 9261 57795 0 0% 0 0 0
30k_methods (click) 2175539 1658674 5780 19394 0 0% 0 0 0
cfunc_itself (click) 163123 126039 6 40 0 0% 0 0 0
fib (click) 161587 125647 6 29 0 0% 0 0 0
getivar (click) 163315 128158 6 56 0 0% 0 0 0
keyword_args (click) 163955 126680 7 42 0 0% 0 0 0
respond_to (click) 165235 127493 6 55 0 0% 0 0 0
setivar (click) 163251 126682 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.