YJIT Benchmarks

Details for Benchmarks at 2022-06-02 19:12:56

Overall YJIT is 36.4% faster than interpreted CRuby!
On Railsbench specifically, YJIT is 26.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 MJIT warmups MJIT iters YJIT warmups YJIT iters
activerecord 5 194 75 194 20 194
hexapdf 5 15 20 15
liquid-render 5 138 75 138 20 138
mail 5 108 75 108 20 108
psych-load 5 15 75 15 20 15
railsbench 5 15 75 15 20 15
binarytrees 5 67 75 67 20 67
chunky_png 5 29 75 29 20 29
discourse 5 37 75 37 20 37
erubi 5 48 75 48 20 48
erubi_rails 5 793 75 793 20 793
fannkuchredux 5 15 52 15 20 15
lee 5 22 75 22 20 22
nbody 5 275 75 275 20 275
optcarrot 5 15 75 15 20 15
rubykon 5 15 26 15 20 15
30k_ifelse 5 56 75 56 20 56
30k_methods 5 22 29 22 20 22
cfunc_itself 5 424 75 424 20 424
fib 5 319 75 319 20 319
getivar 5 756 75 756 20 756
keyword_args 5 375 75 375 20 375
respond_to 5 105 75 105 20 105
setivar 5 1868 75 1868 20 1868
str_concat 5 201 75 201 20 201

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) 1020123 758417 131 1278 0 0% 0 0 0
hexapdf (click) 1119899 879211 682 7742 9 0% 0 0 0
liquid-render (click) 501467 384899 150 1506 2 0% 0 0 0
mail (click) 935707 675737 374 5749 15 0% 0 0 0
psych-load (click) 339675 255124 68 457 1 0% 0 0 0
railsbench (click) 2637275 1926228 1436 9822 16 0% 0 0 0
binarytrees (click) 174107 130445 13 58 0 0% 0 0 0
chunky_png (click) 376987 281990 88 968 0 0% 0 0 0
discourse (click) 5939035 4407642 3197 25386 84 0% 2 0 0
erubi (click) 319515 242786 10 79 0 0% 0 0 0
erubi_rails (click) 1949019 1402526 300 1970 4 0% 0 0 0
fannkuchredux (click) 186843 140282 10 188 0 0% 0 0 0
lee (click) 378395 283827 58 622 0 0% 0 0 0
nbody (click) 182299 136785 12 158 0 0% 0 0 0
optcarrot (click) 514907 442895 207 3571 20 0% 0 0 0
rubykon (click) 317403 250617 144 1534 1 0% 0 0 0
30k_ifelse (click) 5563291 4350769 9265 57804 0 0% 0 0 0
30k_methods (click) 2176923 1658235 5784 19361 0 0% 0 0 0
cfunc_itself (click) 171355 128213 10 49 0 0% 0 0 0
fib (click) 171227 128682 10 38 0 0% 0 0 0
getivar (click) 171611 130332 10 65 0 0% 0 0 0
keyword_args (click) 172187 128854 11 51 0 0% 0 0 0
respond_to (click) 173467 129667 10 64 0 0% 0 0 0
setivar (click) 172955 129717 10 38 0 0% 0 0 0
str_concat (click) 172955 130037 12 62 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.