YJIT Benchmarks

Details for Benchmarks at 2022-05-12 07:13:12

Overall YJIT is 30.8% faster than interpreted CRuby!
On Railsbench specifically, YJIT is 27.7% 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 187 75 187 20 187
hexapdf 5 15 20 15
liquid-render 5 136 75 136 20 136
mail 5 106 75 106 20 106
psych-load 5 15 75 15 20 15
railsbench 5 15 75 15 20 15
binarytrees 5 64 75 64 20 64
chunky_png 5 29 75 29 20 29
discourse 5 32 75 32 20 32
erubi 5 47 75 47 20 47
erubi_rails 5 815 75 815 20 815
fannkuchredux 5 15 51 15 20 15
lee 5 21 75 21 20 21
nbody 5 275 75 275 20 275
optcarrot 5 15 75 15 20 15
rubykon 5 15 25 15 20 15
30k_ifelse 5 55 75 55 20 55
30k_methods 5 22 29 22 20 22
cfunc_itself 5 443 75 443 20 443
fib 5 320 75 320 20 320
getivar 5 770 75 770 20 770
keyword_args 5 380 75 380 20 380
respond_to 5 103 75 103 20 103
setivar 5 1861 75 1861 20 1861
str_concat 5 196 75 196 20 196

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) 1009819 750106 131 1238 0 0% 0 0 0
hexapdf (click) 1111451 871711 683 7702 10 0% 0 0 0
liquid-render (click) 507547 388973 150 1580 2 0% 0 0 0
mail (click) 885019 640837 374 5275 15 0% 0 0 0
psych-load (click) 340187 255601 68 462 1 0% 0 0 0
railsbench (click) 2622811 1914983 1436 9818 16 0% 0 0 0
binarytrees (click) 171867 128729 13 58 0 0% 0 0 0
chunky_png (click) 382619 285138 88 1026 0 0% 0 0 0
discourse (click) 5837275 4330267 3161 24851 81 0% 2 0 0
erubi (click) 319451 242761 10 79 0 0% 0 0 0
erubi_rails (click) 1933851 1391498 300 2015 4 0% 0 0 0
fannkuchredux (click) 185371 139131 10 188 0 0% 0 0 0
lee (click) 377755 283390 58 618 0 0% 0 0 0
nbody (click) 181339 135930 12 158 0 0% 0 0 0
optcarrot (click) 512539 441179 207 3571 20 0% 0 0 0
rubykon (click) 317403 250332 144 1543 2 0% 0 0 0
30k_ifelse (click) 5560923 4349053 9265 57804 0 0% 0 0 0
30k_methods (click) 2176027 1657515 5784 19361 0 0% 0 0 0
cfunc_itself (click) 170395 127358 10 49 0 0% 0 0 0
fib (click) 168859 126966 10 38 0 0% 0 0 0
getivar (click) 170139 129181 10 65 0 0% 0 0 0
keyword_args (click) 171227 127999 11 51 0 0% 0 0 0
respond_to (click) 172507 128812 10 64 0 0% 0 0 0
setivar (click) 170587 128001 10 38 0 0% 0 0 0
str_concat (click) 170587 128321 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.