YJIT Benchmarks

Details for Benchmarks at 2022-05-13 07:14:29

Overall YJIT is 30.8% faster than interpreted CRuby!
On Railsbench specifically, YJIT is 27.5% 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 188 75 188 20 188
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 34 75 34 20 34
erubi 5 45 75 45 20 45
erubi_rails 5 789 75 789 20 789
fannkuchredux 5 15 74 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 54 75 54 20 54
30k_methods 5 21 29 21 20 21
cfunc_itself 5 444 75 444 20 444
fib 5 320 75 320 20 320
getivar 5 763 75 763 20 763
keyword_args 5 374 75 374 20 374
respond_to 5 103 75 103 20 103
setivar 5 1862 75 1862 20 1862
str_concat 5 207 75 207 20 207

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) 1014043 754480 131 1233 0 0% 0 0 0
hexapdf (click) 1119899 878800 682 7747 10 0% 0 0 0
liquid-render (click) 512027 392429 150 1625 2 0% 0 0 0
mail (click) 916379 662514 374 5565 15 0% 0 0 0
psych-load (click) 339547 255124 68 457 1 0% 0 0 0
railsbench (click) 2636635 1926172 1436 9817 16 0% 0 0 0
binarytrees (click) 171739 128594 13 58 0 0% 0 0 0
chunky_png (click) 383707 286073 88 1026 0 0% 0 0 0
discourse (click) 5954715 4418480 3196 25505 84 0% 2 0 0
erubi (click) 319451 242786 10 79 0 0% 0 0 0
erubi_rails (click) 1952027 1404353 300 2011 4 0% 0 0 0
fannkuchredux (click) 185883 139427 10 188 0 0% 0 0 0
lee (click) 378267 283852 58 622 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) 316443 249393 144 1528 1 0% 0 0 0
30k_ifelse (click) 5560923 4349053 9265 57804 0 0% 0 0 0
30k_methods (click) 2176091 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) 170651 129477 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.

Far Too Many Details

These are links to HTML reports on GitHub with far, far too much detail about the benchmarking runs per-platform.

Autogenerated by continuous_reporting/generate_and_upload_reports.rb script.