Runtime performance
How fast the programs Rue compiles actually run. Every point is a whole process — spawn to exit — of a release-quality build, measured on the pinned reference regime and judged against a committed correctness oracle before it is allowed to be a measurement at all. The companion series for the compiler itself is on the compiler performance page.
Programs
One card per measured program. Select one to plot it. The figure is the median of independent fresh processes at the newest measured commit, with the median absolute deviation of those samples beside it.
Wall time —
Whole-process wall time across compiler commits, oldest first. The axis starts at zero, so the height of a point is the time it took rather than its distance from a chosen floor. The runtime workloads consume data, and ADR-0072 records that data's identity with every observation instead of pinning it. So a movement in the series has two possible causes — the compiler changed, or the input did — and only the first is a result. Every point carries the digest of the input it consumed and of the program's own source. A segment is a run of consecutive points that agree on both. Raw medians are comparable inside one and are not comparable across one, so the chart draws each segment as its own stretch, the deltas below are taken within a segment, and the trailing window a flag is measured against restarts at every boundary. A single line drawn across a corpus change would be a picture of a trend that did not happen. The cross-segment signal ADR-0072 defines is the ratio of Rue's time to a pinned peer tool's time on the same corpus. That needs the peer leg, which is not collected yet — see below.Why the line breaks
Segments
The same series as a table, one row per identity-matched stretch. This is where the figures live for a reader who cannot use the chart, and it is the honest place to compare two medians: within a row, never between them.
| Segment | Commits | Input | Program | Median wall time | Change within segment |
|---|
Against other tools
ADR-0072's headline question is order-of-magnitude placement against production software: gazette, a static site generator written in Rue, building the live rue-lang.dev corpus beside pinned Zola and Hugo building the identical corpus under a feature-parity configuration. All three tools have these features disabled: syntax highlighting, search-index generation, and HTML minification, along with Sass and CSS building, live reload, image processing, taxonomies, and pagination. The parity configurations are versioned in the repository beside the template ports. This compares a corpus-specialized Rue program against general-purpose tools. Gazette implements the subset of Markdown, shortcodes, and template features this corpus actually uses; Zola and Hugo implement all of theirs. Gazette renders through its general engine paths — corpus-specific fast paths are out of bounds — but a subset engine is structurally leaner than a general one, and no amount of validation removes that asymmetry.Tool Corpus scale Threads Median wall time Versus gazette Version
No peer measurements have been collected yet. Gazette, the pinned Hugo toolchain, and the parity configurations do not exist in the repository yet; this table fills in when the cross-tool leg of collection first runs. Nothing is estimated here in the meantime.
Field notes
Disclosures
What a flag means here
A program is flagged when its median differs from the median of the trailing window of prior in-segment measurements by more than k times the two dispersions combined. It is measured against noise rather than against a percentage, it has no direction — a large speedup flags exactly as a regression does — and the window it compares against restarts at every corpus or program discontinuity.
Runtime flags carry no CI gate in v1. ADR-0072 puts the runtime series deliberately outside the required-CI gates: a stalled runtime series has a remedy measured in parser work, so it surfaces as a staleness note and a maintainer triage item, never a repository-wide block.
Memory and binary size
Measurement regime
Collection health
Download the derived data — rebuilt at site build time from the raw runtime records on the performance-data-v1 branch, which stores observations and nothing derived. Medians, dispersions, segments, and every comparison on this page are recomputed from those samples; none of them is stored.