docs: the T4 has never run a kernel here - #92
Merged
Merged
Conversation
docs/LIMITATIONS.md said both "Only 8.6 (A10G) and 7.5 (T4) have ever had a kernel measured on them here" and, twenty lines later, "nothing has been measured on a T4". The evidence is with the second: docs/research-baseline.md records the tier-2 box as a g5.xlarge with an A10G, chosen over the T4 by the operator, and model-calibration.toml names one device. Not a footnote. README points at this file twice -- read it before trusting a result -- and the paragraph exists to tell a reader which rows of the model's device table are experience and which are documented capacity. Someone deciding whether to act on a --cc 7.5 ranking was reading a sentence saying it had been validated on silicon. Five of the six rows are capacity, not four. Signed-off-by: Vyncint Ng <chivy.nguyen@manabie.com>
vyncint
force-pushed
the
docs/limitations-t4-claim
branch
from
September 22, 2026 06:14
bb0e29f to
bf077e9
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
docs/LIMITATIONS.mdsays both of these, twenty lines apart:They cannot both be true, and the evidence in the repository is with the second:
docs/research-baseline.md:16— the tier-2 box is an AWSg5.xlarge, NVIDIA A10G (sm_86, cc 8.6), "chosen over the T4 by the operator; barely above T4 spot"model-calibration.toml:11—device = "NVIDIA A10G (cc 8.6)", and it is the only device in the fileruns/holds one committed sweep,reduce-stable-metal, on an Apple M4 ProSo line 147 claimed a hardware validation at cc 7.5 that never happened.
This is not a typo in a footnote.
README.mdpoints at this file twice — "the honest edges live in docs/LIMITATIONS.md. Read that before trusting a result" — and the paragraph exists specifically to tell a reader which rows of the model's device table are experience and which are only documented capacity. Someone deciding whether to act on a--cc 7.5ranking was reading this exact sentence to make that decision, and it told them the part had been measured.Five of the six rows are capacity rather than experience, not four. The corrected paragraph says so, names the two files that establish it, and keeps a parenthetical recording the contradiction — a claim that was wrong once is worth marking, so nobody restores it from memory.
I checked the rest of the file for the same shape: no other capability claim in it is contradicted by
research-baseline.mdormodel-calibration.toml.Closes #73