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

feat(augaman): second, fixtures-only instance on fv-ml1 GPU 1; CPU vs GPU speed bench (v0.1.2 baseline)

Browse Source 
Prime asked for augaman on fv-ml1's utility card, beside vllm-coder. Mirror
augaman-dev's f77164f compose, which parameterises the GPU reservation (GPU_ID,
default 0) and the Homepage card name (CARD_SUFFIX). esh-ml1's resolved config is
unchanged: same config hash, no recreate.

On fv-ml1: augaman:0.1.2 built on-box from the tag, GPU_ID=1, healthy on CUDA
at 1264 MiB, and pytest -m gpu tests/vision passes 3/3 on the Blackwell. It has
its own gallery and no gallery backup, so it is fixtures-only. The host's raw
restic copy of /var/lib/docker/volumes is not a consistent SQLite backup.

docs/pfi/augaman-speed-bench/ holds the harness (augaman-dev's recipe plus a
no-face control frame and a face-count check on every response), the raw rows
and the summary. Server-side, one face:
- esh-ml1 GPU 144 ms
- fv-ml1 GPU 75 ms
- fv-ml1 CPU on 6 cores 152 ms
- esh-ml1 CPU 888 ms
It agrees with augaman-dev's independent esh-ml1 measurement once each
harness's floor is subtracted. This is the before for v0.1.3's detector fix.
This commit is contained in:
vh
2026-09-27 00:28:20 -07:00
parent 2cd5048447
commit 317868dc7e
10 changed files with 774 additions and 10 deletions
Download Patch File Download Diff File Expand all files Collapse all files
stacks/augaman/.env.example
+12 -2
View File
@@ -11,9 +11,19 @@ IMAGE=augaman:0.1.2
PORT=8040
HOST_IP=10.0.50.80
# The host's card index for the GPU reservation (default 0). The container always
# sees its one card as index 0, so AUGAMAN_CUDA_DEVICE_ID never changes.
# esh-ml1: 0 (the only card) fv-ml1: 1 (the utility card, beside vllm-coder)
GPU_ID=0
# Appended to the Homepage card name so the two instances are distinguishable.
# Note the leading space. esh-ml1 (the primary) leaves it empty.
# fv-ml1: CARD_SUFFIX=" (fv-ml1)"
CARD_SUFFIX=
# Where the backup CLI writes gallery.db. Owned 10001:10001 (the container user),
# mode 0700. It is the restic stage dir, so the backup run that copies the gallery here
# is the same run that ships it off-box (README "Backup").
# mode 0700. On esh-ml1 it is the restic stage dir, so the backup run that copies the
# gallery here is the same run that ships it off-box (README "Backup").
# fv-ml1 (fixtures-only, no scheduled gallery backup): /opt/docker/backup/augaman.
BACKUP_DIR=/var/lib/restic/stage/augaman
# >= 32 visible-ASCII characters. Source of truth is the vault: