Skip to content

27B contended throughput, recorded as contended (#440/#441) - #2340

Closed
joelteply wants to merge 1 commit into
canaryfrom
feat/qwen3-27b-throughput
Closed

27B contended throughput, recorded as contended (#440/#441)#2340
joelteply wants to merge 1 commit into
canaryfrom
feat/qwen3-27b-throughput

Conversation

@joelteply

Copy link
Copy Markdown
Contributor

6 samples on the live M5 lane: median 6.56 tok/s at a 22,528 per-slot window with busy_slots = 2 of 4 every time. MTP held 83.9–84.8% draft acceptance throughout — flat while t/s moved 1.4×, so the draft head is not the variance source.

Deliberately NOT written into tokens_per_second. That field is #441's single-stream expectation; 6.56 is contended. Recording it would drop the collapse floor from ~4.3 to ~1.6 tok/s and let a real collapse pass silently. The pinned 17.2 stays.

Both numbers are true and measure different machines. The gap is the finding: the sentinel can't distinguish contended from degraded, because nothing records concurrency at measurement time — the sibling of the window axis landed in #2339, and #441's remaining half.

Also corrects my own earlier claim: -c 89280 is the total across 4 slots, not the live window. Per-slot is 22,528 vs the catalog's 19,712 — 1.14×, not 4.5×.

Comment-only change to one file. cargo check 0, model_registry tests 0.

🤖 Generated with Claude Code

https://claude.ai/code/session_01LoTjvf5j3Ez13g6k8mRkFo

…441)

MEASURED 2026-08-20, 6 samples of 150 tok on the live M5 lane: 4.74 / 5.25 /
6.55 / 6.57 / 6.66 / 6.67 tok/s, median 6.56, at a 22,528 PER-SLOT window
with `busy_slots = 2` of 4 on EVERY sample.

NOT written into `tokens_per_second`, deliberately. That field is what #441's
collapse alarm reads as the SINGLE-STREAM expectation, and 6.56 is a contended
rate — `ThroughputBaseline`'s own doc says "single sequence". Putting it there
would drop the alarm's floor from ~4.3 to ~1.6 tok/s and let a genuine collapse
pass silently. The pinned 17.2 stays.

Both numbers are true; they measure different machines. THE GAP IS THE POINT:
the sentinel cannot currently tell "contended" from "degraded" because nothing
records concurrency at measurement time. That is the sibling of the window axis
landed in #2339, and it is #441's remaining half.

MTP held 83.9-84.8% draft acceptance across all six, and 80.3-84.3% across
three earlier samples on a different prompt. Acceptance is FLAT while t/s moves
1.4x, so the draft head is not the variance source.

Also corrects my own earlier reading: I took `-c 89280` off the lane argv and
called it the live window. It is the TOTAL across 4 slots; per-slot is 22,528
against the catalog's 19,712 — 1.14x, not the 4.5x I claimed. The window was
never the explanation.

cargo check exit 0; model_registry tests exit 0 (both read by exit code).

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01LoTjvf5j3Ez13g6k8mRkFo
@joelteply

Copy link
Copy Markdown
Contributor Author

Superseded by #2341, which carries this commit plus the #441 concurrency axis — combining per Joel.

@joelteply joelteply closed this Aug 20, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant