refact(comments): state the mechanism, not the incident
Every comment that invoked a 'law' (50 word-boundary sites across 28 tracked files) now states what is going on and why, in terms that transfer to any project: gate twins drift until one side greenlights what the other refuses; a tag re-points while a digest pins; a restrictive engine behavior belongs to the runtime that imposed it and must be re-tested, not inherited; a speculative head is tensors in the file, not a flag; snapshot links dangle where the container resolves them; exit 0 is a clean stop to systemd, so a self-exiting daemon on on-failure goes dark reporting success. Event narratives and dates are gone from these comments; the mechanics carry the argument. Behavior-identical: bash -n, py_compile, yaml parse, full bats suite 408/408 green. One symbol rename rides along (stack script local scale_law -> scale_contract, with its log text).
This commit is contained in:
1 parent
65bd5ccea7
commit
d4ce76b68b
28 files changed
+195
-164
No files matched your search
+14
-12
@@ -115,15 +115,16 @@ FRANK_ARCHON_TP=2
|
||||
FRANK_ARCHON_TP_WIRE=wht6
|
||||
# Decode slots: TWO, so the served window is a CAPACITY CONTRACT — two
|
||||
# concurrent conversations of --max-model-len fit the KV pool (see the KV
|
||||
# block below). The "seqs 2 cannot boot" law is NOT radiance's: it was the
|
||||
# tcclaviger vLLM fork's torch.compile shape specialization on
|
||||
# query_start_loc (ConstraintViolationError, measured 2026-10-02, retired
|
||||
# with that runtime). Radiance booted seqs 2 at the fp8-native first boot,
|
||||
# and the 2026-10-06 decode sweep measured seqs 2 and 3 statistically tied
|
||||
# (30.9-33.1 t/s, inside the +-3% noise floor). Side benefit: the fused TP
|
||||
# all-reduce is declared over seqs x (1 + spec) = 6 rows, under the 25-row
|
||||
# bound at which the wht6 wire stays EXACT (single-sequence decode and any
|
||||
# step of <= 25 rows is bit-exact; only busier steps are lossy).
|
||||
# block below). Slot-count limits observed on other runtimes do NOT
|
||||
# transfer: a "this slot count cannot boot" refusal is usually that
|
||||
# runtime's compiler specializing shapes (e.g. a ConstraintViolationError
|
||||
# from shape specialization on query_start_loc), not a property of the
|
||||
# engine now running. This engine boots seqs 2, and seqs 2
|
||||
# vs 3 decode measurements land inside each other's noise floor. Side
|
||||
# benefit: the fused TP all-reduce is declared over seqs x (1 + spec) = 6
|
||||
# rows, under the 25-row bound at which the wht6 wire stays EXACT
|
||||
# (single-sequence decode and any step of <= 25 rows is bit-exact; only
|
||||
# busier steps are lossy).
|
||||
FRANK_ARCHON_MAX_SEQS=2
|
||||
# Served window. Native is 262,144; 200,000 is the publisher's production
|
||||
# value (compose) and what models.yml's contextWindow must quote — a longer
|
||||
@@ -203,9 +204,10 @@ FRANK_ARCHON_MAX_BATCHED_TOKENS=2048
|
||||
# (104 GiB available with the service loaded).
|
||||
FRANK_ARCHON_PREFIX_HOST_MIB=8192
|
||||
FRANK_ARCHON_PREFIX_DISK_MIB=65536
|
||||
# Frank's pin law: the PLE n-gram table (47.7 GiB) serves from pinned host
|
||||
# RAM the cards read. `ram` REFUSES the start if the memlock limit is too
|
||||
# small — the unit's LimitMEMLOCK=infinity is the other half of this law.
|
||||
# The PLE n-gram table (47.7 GiB) serves from pinned host RAM the cards
|
||||
# read. `ram` REFUSES the start if the memlock limit is too small — a
|
||||
# named refusal beats a mid-load allocator failure — and the unit's
|
||||
# LimitMEMLOCK=infinity is the other half of the arrangement.
|
||||
FRANK_ARCHON_NGRAM_PLACEMENT=ram
|
||||
# TTM preflight: the pinned ledger (2 x 44 GiB pools + 47.7 GiB PLE + 8 GiB
|
||||
# prefix host = ~147 GiB) rides TTM's shared pages, capped by ttm's
|
||||
|
||||
Reference in new issue
Block a user