Skip to content

fix(distribution): anchor left edge at fieldMin, not zero - #166

Merged
Flotapponnier merged 1 commit into
devfrom
fix/distribution-min-baseline
May 29, 2026
Merged

fix(distribution): anchor left edge at fieldMin, not zero#166
Flotapponnier merged 1 commit into
devfrom
fix/distribution-min-baseline

Conversation

@Flotapponnier

Copy link
Copy Markdown
Collaborator

Solves the narrow-range compression on benches like solana-tx-landing-latency where all p50 values cluster at the left edge of the track.

Math sample (solana-tx-landing-latency, fieldMin=2, fieldMax=14 slots):

  • Before: all p50=2 → 14% of track (all dots stuck together)
  • After: leader p50=2 → 0%, Jito p50=3 → 8%, p99s spread across the full track

Affects every bench in distribution view — narrow-range ones benefit visibly, wide-range ones (already log scale) get the same min anchor too.

Narrow-range benches with small absolute minimums collapse every median
dot into a single sliver at the left. solana-tx-landing-latency is the
canonical case: 5 providers all have p50 = 2 slots on a 14-slot field,
so every median lands at 14 % of the track and there is no visible
spread between the leaders.

Switch both linear and log scale to use fieldMin as the left baseline.
The leader now sits at 0 % and laggards spread across the full track.
Footer always shows 'min X' so the reader knows the chart is relative
to observed range, not absolute zero.
@Flotapponnier
Flotapponnier merged commit cfe4867 into dev May 29, 2026
1 check failed
Flotapponnier added a commit that referenced this pull request May 29, 2026
fix(distribution): anchor left edge at fieldMin, not zero
@Flotapponnier
Flotapponnier deleted the fix/distribution-min-baseline branch May 29, 2026 09:58
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