|
|
@@ -171,3 +171,14 @@ at 4-5x the turn latency** (prefill is ~7x slower — the harness scores it as
|
|
|
responsiveness 23). TensorFold 2x is the long-generation / batch shape; the 4x
|
|
|
SGLang lane remains the interactive-agent shape. Not purity-matched: thinking
|
|
|
effort 75 vs 100, EXL3 2.9bpw vs fp8.
|
|
|
+
|
|
|
+**Status 2026-10-19:** the lane is now a real sm121 recipe —
|
|
|
+`recipes/dsv41-flash-1017-2x-tensorfold` + `docker-images/dsv41-tf-1017` + the
|
|
|
+`tensorfold_1017_prepare` built-in host script. `sm121 serve --recipe
|
|
|
+dsv41-flash-1017-2x-tensorfold --cluster 2nodes-dac` stages, builds, syncs and
|
|
|
+launches it end to end (API ready ~4 min after the 24.5 GB image sync), and
|
|
|
+`sm121 stop` closes the runlock. The upstream repo's **vLLM profile on the same
|
|
|
+weights is blocked** in our environment — the exact failure and the fix options
|
|
|
+are in the last section of that lane's `NOTE.md` (the NFS Engram volume carries
|
|
|
+only NAS symlinks that dangle inside the worker's vLLM container; rsync mode
|
|
|
+wants 196 GiB free on the worker).
|
