|
|
@@ -744,3 +744,25 @@ Key findings:
|
|
|
4.84M KV) — needs a production recipe + operator sign-off; (2) r18 2x
|
|
|
adoption as the new 2x default (157 vs 153 baseline); (3) DCP4+nvfp4 KV
|
|
|
combined cell; (4) eugr lanes stay demoted.
|
|
|
+
|
|
|
+## r12/r18 image separation (2026-09-06, operator direction)
|
|
|
+
|
|
|
+The `glm53-jovian-r12:local` tag pointing at r18 content was wrong — separate
|
|
|
+now, no mixing:
|
|
|
+- `docker-images/glm53-jovian-r18/` — self-contained r18 build dir (r18
|
|
|
+ versions.env pins 582+646, fixed kv-cache-cleanup patch, re-staged
|
|
|
+ deps-src with FA+MSA cutlass, source tarballs vllm `67e7e6e` / b12x
|
|
|
+ `b58f34ea`). Image tag: `glm53-jovian-r18:local` (renamed on all 4 nodes
|
|
|
+ from the r12 tag; content unchanged, built during the night shift).
|
|
|
+- `docker-images/glm53-jovian-r12/` — restored via `git checkout 582343c`
|
|
|
+ to the genuine r17 state (pins 550–557, original kv-cache-cleanup patch).
|
|
|
+ Image tag `glm53-jovian-r12:local` currently points at NOTHING (removed
|
|
|
+ from nodes) — an r17 rebuild is possible but NOT done: the r17-era
|
|
|
+ deps-src staging is unrecoverable (untracked + overwritten), so a rebuild
|
|
|
+ today would use the r18 deps staging (FA/MSA cutlass populated) and be a
|
|
|
+ subtly different image than the original r17 anchor. If the r17 A/B
|
|
|
+ anchor is ever needed again, re-cut the r17-era deps first.
|
|
|
+- Recipes: `glm53-flash-nvfp4-r18{,-4x,-4x-dcp4,-4x-nvfp4kv,-dflash2}`
|
|
|
+ (new) → r18 tag/dir; `glm53-flash-nvfp4-r17abi` unchanged → r12 tag/dir.
|
|
|
+- Source tarballs (vllm-src/b12x-src) are local build artifacts — now
|
|
|
+ gitignored; deps-src already was.
|
