From 0118e57c839630b52330595275b6b9f46803c908 Mon Sep 17 00:00:00 2001 From: Vuong Hoang Date: Sun, 27 Sep 2026 01:13:22 -0700 Subject: [PATCH] memory: augaman v0.1.3 live on both hosts; bench before/after recorded --- persistent-memory.md | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/persistent-memory.md b/persistent-memory.md index e110e30..bd83558 100644 --- a/persistent-memory.md +++ b/persistent-memory.md @@ -157,9 +157,10 @@ _As of 2026-09-26 ~1620 PT._ is theirs. Their next release pins the container gid to 10001; nothing is owed by infra-ops. - **Second instance on fv-ml1 GPU 1 (Prime, 2026-09-27)**, `GPU_ID=1`, **fixtures-only, no gallery backup**, separate gallery. Its role (bench-only vs future primary) is Prime's call. -- **Speed bench v0.1.2 "before"** (`docs/pfi/augaman-speed-bench/`), server-side one face: - esh GPU 144 ms, fv GPU 75 ms, fv CPU (6 cores) 152 ms, esh CPU 888 ms. **OWED: re-run on - v0.1.3** (detector gets one session per canvas, ~2× faster) when augaman-dev tags it. +- **v0.1.3 live on BOTH hosts (2026-09-27 ~0105 PT).** Speed bench (`docs/pfi/augaman-speed-bench/`), + server-side one face, v0.1.2 → v0.1.3: esh GPU 144 → 48 ms, fv GPU 75 → 27 ms. CPU mode + REGRESSED (fv CPU6 152 → 205 ms; suspected ORT thread-pool spinning) and is reported to + augaman-dev; neither deployment uses CPU mode. The fv-ml1 instance's role is still Prime's call. ### esh-ml1