2 Commits

Include renames

Author	SHA1	Message	Date
vh	3132a16ca0	fv-ml1: finish the renumber the cutover missed -- 16 dead dashboard links ... Every fv-ml1 link on the Homepage dashboard was broken. Measured against the live dashboard API before the fix: 16 entries pointing at the dead 10.250.50.54 and zero at the live 10.251.50.54, covering gen, M.O.G.-SEC, Scriberr, Embed, Rerank, Reward, Coder, Dockge and six dormant seats. The miss was structural, not careless. fv-ml1-rename-sweep.sh works from an allowlist assembled from files that mention the HOST, and a homepage.href label mentions only an IP -- so every stack whose sole stale reference was a label fell outside it. The allowlist now covers those 24 files, and records how to derive the list next time (grep the old address, subtract history) rather than enumerating from memory. History is still untouched, and the exclusions are now written down with the reason each one keeps the old address: recorded benchmark results, whose base_url is part of a measurement's provenance; the one LiteLLM comment preserving a retired hand-test endpoint; and the cutover runbooks, where the old address is the subject matter. Two bugs found while applying it, both fixed here: - deploy-stack.sh rejected any stack name containing a dot, so qwen3.5-122b, qwopus3.5-122b and mistral-medium-3.5 could not be deployed by the script at all. The check exists to stop path traversal, which means rejecting ".." and "/" -- not every dot. Traversal is now rejected explicitly and tested. - stacks/scriberr/.env.example allowed CORS only from the dead IP and from scriberr.ana.internal, which no longer resolves; the box is at the fv site and DNS already carries scriberr.fv.internal. The live .env had both stale origins, i.e. an allowlist with nothing reachable in it. Host side, applied separately: canonical pushed for the 16 stacks whose only difference from the host was this renumber, and an in-place address-only fix for the nine whose host copy has genuinely drifted or has no canonical copy, so that drift survives for a deliberate reconciliation instead of being clobbered. Every compose.yaml on fv-ml1 now reads 10.251.50.54. The labels themselves only take effect at container creation, so the running containers still need recreating.	2026-09-12 23:05:29 -07:00
vh	74f596b1d3	feat(gen-seat): mixed NVFP4+FP8 requant — +18% decode at equal MTP acceptance ... Re-quantizes the fleet `gen` seat from weight-only NVFP4A16 to a mixed-precision build: NVFP4 W4A4 for layers 0-55 MLPs, FP8 W8A8 for the attention projections / linear_attn / lm_head / layers 56-63 MLPs, FP8 KV cache. Replicates the scheme of unsloth/Qwen3.8-27B-NVFP4 on the abliterated weights. The queued task named this "W4A8" (NVFP4 weights + FP8 activations). That checkpoint cannot be served: vLLM 0.24's compressed-tensors dispatcher (compressed_tensors.py:704-713) accepts NVFP4 weights with either no input quantization (W4A16, which forces the Marlin kernel) or NVFP4 input quantization (W4A4) -- anything else, FP8 included, raises ValueError at load. CompressedTensorsW4A8Fp8 is INT4 weights gated on an exact-sm90 check, so it is closed on Blackwell twice over. The ~20% intuition was correct; the scheme name was not. Getting FP8 into the mix has to be done per-layer-group. Established the gain before spending GPU time: unsloth's build was already on-box, so serving it as a probe measured +19.1% over our seat at identical MTP acceptance -- a kernel-level result, no requant needed to learn it. Measured, cache-busted, bs=1: decode 80.12 -> 94.53 tok/s (+18.0%) MTP acceptance 47.8% -> 47.7% (unchanged) perplexity (n=6) 6.941 -> 7.059 (+1.7%) abliteration 4/4 -> 4/4 (preserved) weights on disk 27.7 -> 22.5 GB (-19%) Surface test green on the live seat: plain chat, vision, tool calling, thinking split, 36K-token needle retrieval, streaming. All 7 LiteLLM aliases verified routing. GEN_GPU_MEM_UTIL 0.45 -> 0.43: the new weights are 5.2 GB smaller, and at 0.45 the seat absorbed that slack as KV, leaving meromero-charrp 0.18 GiB short of its budget on the shared GPU0 -- it crash-looped. Handing the space back leaves gen 422K tokens of KV (1.6x its 262K context) and both seats co-resident at 89.8/97.9 GB. Also records two measured negatives so they are not re-chased: GEN_SPEC_TOKENS is already optimal at 3 (swept 2/3/4/5 -> 77.1/80.1/78.7/ 75.9 tok/s), and vLLM's prompt_logprobs are ~uniform while speculative decoding is on, so perplexity must be measured with spec off. Pipeline, acceptance harness and raw measurements land in services/gen-seat-mixed-quant/. Rollback is one .env line; the previous build is untouched at /tank/aimodels/qwen38-27b-uncensored-nvfp4.	2026-08-15 02:21:00 -07:00