Skip to content

Dashboard: label the prefetch lane meter Utilization and add its sparkline - #356

Merged
samsoir merged 1 commit into
develop/0.5.1from
feat/prefetch-utilization-355
Nov 11, 2026
Merged

samsoir merged 1 commit into
develop/0.5.1from
feat/prefetch-utilization-355

Conversation

@samsoir

@samsoir samsoir commented Nov 10, 2026

Copy link
Copy Markdown
Owner

Closes #355

What

The Prefetch System pane's meter row reads Utilization instead of Capacity, with its indent dropped so its values align with the Prefetch row above. Beside the meter a sparkline shows the lane's utilization over the last twelve seconds.

   Prefetch: ● Active │ Cruise │ 42/cyc
Utilization: █████████░  93% │ ▁▁▂▅▇████▇▅▃ │ 1,904 queued

Two choices a reviewer cannot read off the diff:

  • One cell per second, not per draw. The other panes push a sample every draw, and the dashboard draws every 100 ms, so their 12-cell sparklines cover 1.2 s. LaneHistory averages each second into a cell and draws the open second live, so the row covers 12 s and still moves on the next draw.
  • Scaled against a full lane, not the recent peak. Utilization has a ceiling the throughput sparklines lack, so a half-busy lane always draws at half height and agrees with the percentage beside it.

Verification

  • make pre-commit clean: fmt, clippy with -D warnings, full workspace tests.
  • 11 widget tests (6 new) cover the label, the alignment with the Prefetch row, the sparkline position in the row, per-second averaging, absolute scaling, the 12-second window and an unknown lane size reading as idle.
  • Not yet seen in a running dashboard.

CHANGELOG entry under Unreleased.

…kline

The Prefetch System pane's meter shows the share of the prefetch lane in
use, 0% at rest to 100% with every slot busy. It was labelled Capacity,
which names the fixed size rather than the share in use. The row now reads
Utilization, with its indent dropped so its values align with the Prefetch
row above.

Beside the meter a sparkline shows the lane's utilization over the last
twelve seconds. The dashboard draws every 100 ms, so a per-draw history
like the other panes' would cover 1.2 s, too short to read a trend from;
LaneHistory averages each second into one cell instead and draws the open
second live. Cells scale against a full lane rather than the recent peak,
so a half-busy lane always draws at half height and agrees with the
percentage beside it.

Closes #355
@samsoir samsoir added this to the v0.5.1 milestone Nov 10, 2026
@samsoir
samsoir merged commit dbe265e into develop/0.5.1 Nov 11, 2026
2 checks passed
@samsoir
samsoir deleted the feat/prefetch-utilization-355 branch November 11, 2026 04:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant