memory: snapshot — H3 encoder pin resolved; my question had the direction backwards

Checked the disk rather than waiting on comfy-dev. Both builds are there,
pulled a minute apart on Aug 23: a 26 GB int8 and a 15 GB nvfp4-awq.

I had asked whether their nvfp4 pin was set under a Blackwell assumption,
since Ada has no native nvfp4, which would make the int8 file the right
one on the new box. It cannot be. They pinned it on irv-ml1's A6000,
which is Ampere sm_86 and has neither native nvfp4 nor native fp8. Ada
sm_89 supports a strict superset, so a pin that was correct on the weaker
card cannot be invalidated by moving to the stronger one. The migration is
incapable of breaking it.

The pin is about VRAM, not architecture. Eleven gigabytes on a 48 GB card
that also holds a DiT and two VAEs decides whether a graph runs, and a
text encoder runs once per prompt rather than once per diffusion step, so
its throughput matters far less than the DiT's. That also explains why
this pin went the opposite way from their other one without either being
inconsistent. The RTX 6000 Ada is also 48 GB, so nothing relaxes.

Reclassified the 26 GB int8 from orphan to spare: with the extra drives
the destination lands near 14% full, so disk stops being the constraint
and the pin-rot argument says keep it. Question withdrawn to comfy-dev.
This commit is contained in:
vh
2026-09-01 23:05:19 -07:00
parent 12006d287a
commit f099caa238
2 changed files with 36 additions and 9 deletions
+5 -1
View File
@@ -188,7 +188,11 @@ _As of 2026-09-01 — **the GX10 is on the operator's desk, NOT racked. Standing
RETAIN recommended** (two paywalled pins mean a from-source rebuild cannot reproduce the
stack; and under a no-spend striped destination it is the only redundancy). comfy-dev also
found ~215 GiB of unreferenced weights and offers a per-file prune audit — **explicitly NOT
gating**, because pruning all of it still lands the as-bought mirror at 72%.
gating**, because pruning all of it still lands the as-bought mirror at 72%. ✅ **H3 encoder
pin RESOLVED** — infra-ops' nvfp4-vs-int8 question had the direction backwards (pinned on
Ampere sm_86; Ada sm_89 is a strict superset, so the move cannot break it). Pin is about
**VRAM not architecture**; stands. The 26 GB int8 is a **spare, not an orphan** — do not
delete.
→ `persistent-memory.d/2026-09-01-ada-migration-branch-a.md`
- **⏸ Worldtree `route_not_found` awaiting the operator's DEPLOY PUSH.** Approved and landed
by worldtree-dev as `ece0250c` (wire 2.5.0→2.6.0). main auto-deploys demo. Until it ships,