YJIT Benchmarks

Details for Benchmarks at 2022-03-05 07:12:56

Overall YJIT is 32.3% faster than interpreted CRuby!
On Railsbench specifically, YJIT is 30.3% 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 176 75 176 20 176
hexapdf 5 15 20 15
liquid-render 5 154 75 154 20 154
mail 5 123 75 123 20 123
psych-load 5 15 75 15 20 15
railsbench 5 15 75 15 20 15
binarytrees 5 68 75 68 20 68
discourse 5 35 75 35 20 35
erubi 5 47 75 47 20 47
erubi_rails 5 996 75 996 20 996
fannkuchredux 5 15 75 15 20 15
lee 5 22 75 22 20 22
nbody 5 284 75 284 20 284
optcarrot 5 15 75 15 20 15
rubykon 5 15 38 15 20 15
30k_ifelse 5 56 75 56 20 56
30k_methods 5 22 29 22 20 22
cfunc_itself 5 444 75 444 20 444
fib 5 320 75 320 20 320
getivar 5 791 75 791 20 791
keyword_args 5 375 75 375 20 375
respond_to 5 103 75 103 20 103
setivar 5 1874 75 1874 20 1874

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) 989841 758836 185 1199 0 0% 0 0 0
hexapdf (click) 1113809 912528 599 8166 613 7% 0 0 320
liquid-render (click) 486481 384688 143 1503 96 6% 0 0 1
mail (click) 877009 657813 324 5317 125 2% 0 0 39
psych-load (click) 328017 258073 59 434 1 0% 0 0 0
railsbench (click) 2533393 1930684 1297 9351 268 2% 0 0 26
binarytrees (click) 142609 108087 11 59 0 0% 0 0 0
discourse (click) 22938769 11471968 3093 289630 266537 92% 2 0 133
erubi (click) 320977 254037 10 79 0 0% 0 0 0
erubi_rails (click) 1902289 1431617 262 1877 18 0% 0 0 3
fannkuchredux (click) 164753 126142 8 189 0 0% 0 0 0
lee (click) 371281 292325 45 587 69 11% 0 0 12
nbody (click) 151889 115288 10 159 0 0% 0 0 0
optcarrot (click) 487761 428824 198 3576 20 0% 0 0 0
rubykon (click) 284753 229022 140 1540 1 0% 0 0 0
30k_ifelse (click) 5531537 4328298 9263 57805 0 0% 0 0 0
30k_methods (click) 2155537 1644804 5782 19362 0 0% 0 0 0
cfunc_itself (click) 140945 106603 8 50 0 0% 0 0 0
fib (click) 139473 106186 8 39 0 0% 0 0 0
getivar (click) 149713 116550 8 66 0 0% 0 0 0
keyword_args (click) 150225 115047 9 52 0 0% 0 0 0
respond_to (click) 151441 115772 8 65 0 0% 0 0 0
setivar (click) 149457 114863 8 39 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.