Details for Benchmarks at 2021-09-02 15:47:24
Overall YJIT is 35.4% faster than interpreted CRuby!
The basic "faster" measurement is the geomean of all "headlining" x86 benchmarks on this page.
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?
- Headlining benchmarks (x86_64)
- All benchmarks (x86_64)
- CSV speed results (x86_64)
- Headlining benchmarks (AARCH64)
- All benchmarks (AARCH64)
- CSV speed results (AARCH64)
Benchmarks Speed Details
Benchmark Memory Usage Details
Number of Iterations and Warmups Tested
| bench | No JIT warmups | No JIT iters | MJIT3.0 warmups | MJIT3.0 iters | YJIT warmups | YJIT iters |
|---|---|---|---|---|---|---|
| activerecord | 3 | 132 | 3 | 126 | 3 | 179 |
| lee | 3 | 15 | 3 | 20 | 3 | 22 |
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) | 1026982 | 900722 | 185 | ? | 0 | 0 | |||
| lee | (click) | 208946 | 188222 | 86 | ? | 1 | 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.