YJIT Benchmarks

Details for Benchmarks at 2021-11-27 07:10:30

Overall YJIT is 27.4% faster than interpreted CRuby!
On Railsbench specifically, YJIT is 19.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 MJIT warmups MJIT iters YJIT warmups YJIT iters
activerecord 5 184 20 184 75 184 20 184
hexapdf 5 15 20 15 20 15
liquid-render 5 170 20 170 75 170 20 170
mail 5 139 20 139 75 139 20 139
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 596 20 596 75 596 20 596
fannkuchredux 5 15 20 15 55 15 20 15
jekyll 5 15 20 15 35 15 20 15
lee 5 26 20 26 75 26 20 26
nbody 5 342 20 342 75 342 20 342
optcarrot 5 15 20 15 75 15 20 15
rubykon 5 15 20 15 42 15 20 15
30k_ifelse 5 62 20 62 73 62 20 62
30k_methods 5 26 20 26 44 26 20 26
cfunc_itself 5 513 20 513 75 513 20 513
fib 5 383 20 383 75 383 20 383
getivar 5 564 20 564 75 564 20 564
keyword_args 5 303 20 303 75 303 20 303
respond_to 5 132 20 132 75 132 20 132
setivar 5 501 20 501 75 501 20 501

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) 968490 728509 185 1169 0 0% 0 0 0
hexapdf (click) 1074922 856671 595 7985 616 7% 0 0 321
liquid-render (click) 467959 363798 143 1435 95 6% 0 0 1
mail (click) 871978 642356 325 5438 124 2% 0 0 39
psych-load (click) 291809 226488 57 423 1 0% 0 0 0
railsbench (click) 2574114 1921093 1293 9708 263 2% 0 0 26
binarytrees (click) 113189 86085 9 48 0 0% 0 0 0
erubi (click) 269857 209061 8 35 0 0% 0 0 0
erubi_rails (click) 2437410 1742723 260 1976 17 0% 0 0 3
fannkuchredux (click) 129189 98095 6 202 0 0% 0 0 0
jekyll (click) 1890282 1502134 336 4007 180 4% 0 0 0
lee (click) 330538 257098 44 562 67 11% 0 0 12
nbody (click) 122021 92707 8 148 0 0% 0 0 0
optcarrot (click) 451045 392246 196 3566 20 0% 0 0 0
rubykon (click) 254885 204804 139 1529 2 0% 0 0 0
30k_ifelse (click) 5502373 4306409 9261 57794 0 0% 0 0 0
30k_methods (click) 2117477 1614871 5780 19351 0 0% 0 0 0
cfunc_itself (click) 111781 84714 6 39 0 0% 0 0 0
fib (click) 110245 84322 6 28 0 0% 0 0 0
getivar (click) 111589 86617 6 55 0 0% 0 0 0
keyword_args (click) 112229 85139 7 41 0 0% 0 0 0
respond_to (click) 113893 86168 6 54 0 0% 0 0 0
setivar (click) 111909 85357 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.