YJIT Benchmarks

Details for Benchmarks at 2022-05-03 19:17:46

Overall YJIT is 34.0% faster than interpreted CRuby!
On Railsbench specifically, YJIT is 34.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 MJIT warmups MJIT iters YJIT warmups YJIT iters
activerecord 5 192 75 192 20 192
hexapdf 5 15 20 15
liquid-render 5 159 75 159 20 159
mail 5 124 75 124 20 124
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 30 75 30 20 30
discourse 5 39 75 39 20 39
erubi 5 47 75 47 20 47
erubi_rails 5 994 75 994 20 994
fannkuchredux 5 15 74 15 20 15
lee 5 22 75 22 20 22
nbody 5 274 75 274 20 274
optcarrot 5 15 75 15 20 15
rubykon 5 15 28 15 20 15
30k_ifelse 5 54 75 54 20 54
30k_methods 5 22 29 22 20 22
cfunc_itself 5 417 75 417 20 417
fib 5 319 75 319 20 319
getivar 5 763 75 763 20 763
keyword_args 5 378 75 378 20 378
respond_to 5 105 75 105 20 105
setivar 5 1867 75 1867 20 1867
str_concat 5 199 75 199 20 199

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) 1009499 750304 131 1231 0 0% 0 0 0
hexapdf (click) 1114139 873538 683 7697 9 0% 0 0 0
liquid-render (click) 511643 392132 150 1630 2 0% 0 0 0
mail (click) 907547 657056 374 5502 15 0% 0 0 0
psych-load (click) 339931 255503 68 457 1 0% 0 0 0
railsbench (click) 2618587 1912786 1435 9787 16 0% 0 0 0
binarytrees (click) 173211 129880 13 58 0 0% 0 0 0
chunky_png (click) 378843 282986 88 992 0 0% 0 0 0
discourse (click) 5872603 4352080 3187 25115 82 0% 2 0 0
erubi (click) 319387 240345 10 79 0 0% 0 0 0
erubi_rails (click) 1929435 1388503 300 1984 4 0% 0 0 0
fannkuchredux (click) 186715 140282 10 188 0 0% 0 0 0
lee (click) 377883 283480 58 618 0 0% 0 0 0
nbody (click) 182683 137081 12 158 0 0% 0 0 0
optcarrot (click) 513371 442034 207 3571 20 0% 0 0 0
rubykon (click) 317339 250371 144 1525 1 0% 0 0 0
30k_ifelse (click) 5562267 4350204 9265 57804 0 0% 0 0 0
30k_methods (click) 2184091 1661454 5784 19401 0 0% 0 0 0
cfunc_itself (click) 171739 128509 10 49 0 0% 0 0 0
fib (click) 170203 128117 10 38 0 0% 0 0 0
getivar (click) 171995 130628 10 65 0 0% 0 0 0
keyword_args (click) 172571 129150 11 51 0 0% 0 0 0
respond_to (click) 174363 130292 10 64 0 0% 0 0 0
setivar (click) 171931 129152 10 38 0 0% 0 0 0
str_concat (click) 171419 129176 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.