ruby-grape / grape / 33611383907

97%

master: 97%

push

github

Report per-release throughput deltas in the version benchmark

The version_throughput table listed an absolute i/s number per version and
left the reader to divide. The interesting question it should answer is how
much faster Grape got over time, so each pass (no-YJIT and --yjit) now carries
two extra columns: `vs prev`, the change against the previous benched version,
and `vs <first>`, the change against the oldest one. A one-line summary under
the table restates first to last for both passes.

Both deltas are computed per pass on i/s. A version that fails to bench is
skipped as a reference, so `vs prev` always points at the closest version that
produced a number and an `error:` row never breaks the chain. The baseline
column names whichever version comes first in the list rather than hardcoding
3.0.0, so a custom GRAPE_VERSIONS still labels itself correctly.

DEFAULT_VERSIONS moves from 3.0.0, 3.0.1, 3.1.0, 3.1.1, 3.2.0, 3.2.1, master to
3.0.0, 3.1.0, 3.2.0, 3.3.0, 3.3.5, master: the old list predates 3.3, and the
patch releases doubled the runtime without adding a point to the trend.

Co-authored-by: Claude Opus 5 <noreply@anthropic.com>

1236 of 1330 branches covered (92.93%)

Branch coverage included in aggregate %.

3921 of 3989 relevant lines covered (98.3%)

27209.56 hits per line