vh/esh-pfi-infrastructure
1
0
Fork 0
Code Issues 7 Pull Requests Actions Packages Projects Releases Wiki Activity

semif: offline by operator ruling — scriberr needs GPU 1 headroom

Browse Source 
Stopped (not removed) 2026-09-30 0135 PT. Scriberr's Parakeet path hardcodes
5-minute slices; attention memory is quadratic in slice length, so a long file
needs >6 GB and hit CUDA OOM with SemIf resident (~6.7 GB free). GPU 1 now
81,806 MiB used. Durable fix (shorter scriberr slices) deferred to later.
This commit is contained in:
vh
2026-09-30 01:36:18 -07:00
parent 5186b3dc9a
commit 9daf43683d
3 changed files with 13 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
persistent-memory.md
+2 -1
View File
@@ -166,7 +166,8 @@ _As of 2026-09-30 ~0120 PT._
### SemIf on fv-ml1 GPU 1 (2026-09-27, Prime)
- **LIVE: `semif-serve` 0.1.4** (was 0.1.3 until 1014 on 2026-09-27) at `http://10.251.50.54:8032` (`semif.fv.internal`), with order averaging
- **OFFLINE since 2026-09-30 0135 PT (Prime: "take semif offline for now; we'll optimize scriberr later").** Stopped with `docker compose stop`, not removed, to give scriberr back its GPU 1 room. Scriberr's Parakeet path hardcodes `--chunk-len 300`, and the attention memory grows with the square of the slice, so it needs over 6 GB; it hit CUDA OOM at 0124 on a 35-min file with ~6.7 GB free. Stopping SemIf moved GPU 1 from 91,052 to 81,806 MiB used. **Deferred fix (Prime: later):** shorten scriberr's slice to ~120 s in our local build, then SemIf can come back. Embedding cards were ruled out: esh-ml1 has ~4.4 GB free and nh3-ml1 ~5.1 GB. A replacement bench (brokkr's Jev candidates) is running on GPU 3 under a separate harness.
- **Was LIVE: `semif-serve` 0.1.4** (was 0.1.3 until 1014 on 2026-09-27) at `http://10.251.50.54:8032` (`semif.fv.internal`), with order averaging
and the fast kernels. SemIf `23cf1f39`, Qwen3.5-4B `851bf6e8`, BF16; token `semif/api-token`. Code +
contract: `services/semif-serve/`; stack `stacks/semif`. **No consumer yet.**
- 0.1.3 acceptance: 144/144 parity with upstream; averaging through the service 78.6% → 88.1%
servers/fv-ml1/README.md
+1 -1
View File
@@ -182,7 +182,7 @@ embed/rerank/reward trio. GPUs are pinned per container via
**GPU 1 — light / eval / retrieval + char-RP GGUF (~91/98 GB, on-demand):**
> ⚠ **This table is stale (checked 2026-09-27).** Live GPU 1 residents were `scriberr`,
> `vllm-coder`, `vllm-erp-seat` and `vllm-meromero-rp`, plus **`semif`** (:8032, ~8.7 GB resting,
> `vllm-coder`, `vllm-erp-seat` and `vllm-meromero-rp`, plus **`semif`** (**OFFLINE since 2026-09-30, Prime; see `stacks/semif`**; :8032, ~8.7 GB resting when up,
> hard-capped at 12 GiB; `stacks/semif`, since 2026-09-27). Read the host
> (`docker inspect … DeviceRequests`), not this table. (A fixtures-only `augaman` instance ran
> here for about an hour on 2026-09-27 for a speed bench, and was then removed on Prime's call.)
stacks/semif/README.md
+10
View File
@@ -1,5 +1,15 @@
# semif
> ⚠ **OFFLINE since 2026-09-30 0135 PT (Prime: "take semif offline for now").** It was
> stopped (`docker compose stop`, NOT removed) to give scriberr its GPU 1 headroom back:
> scriberr's Parakeet path cuts audio into 5-minute slices and needs over 6 GB, and with
> SemIf resident it had ~6.7 GB and hit CUDA OOM on a 35-minute file. Stopping it moved
> GPU 1 from 91,052 to 81,806 MiB used. The image, weights, config and token are all kept;
> `unless-stopped` keeps it down across a reboot. **Do not restart it without Prime's word.**
> To bring it back: `cd /opt/docker/compose/semif && docker compose start`, but first
> make sure scriberr has its room (the durable fix, shortening scriberr's slice length, is
> deferred by Prime to later). Everything below describes the service as it was deployed.
**SemIf option-logit decisions** on **fv-ml1 GPU 1**, the utility card beside
`vllm-coder`, the erp/meromero seats and scriberr. Deployed 2026-09-27 at Prime's
request. Hosting assessment: infra-hermes, 2026-09-25.