feat(augaman): v0.1.3 on esh-ml1 and fv-ml1; after-bench: GPU ~3x faster, CPU mode regressed

Both hosts are rebuilt from tag v0.1.3 (one ONNX session per detector canvas) and
redeployed. pytest -m gpu tests/vision passes 3/3 on each card.

Server-side for one face, same harness as the v0.1.2 baseline:
- esh-ml1 GPU 144 -> 48 ms
- fv-ml1 GPU 75 -> 27 ms
End to end from nh3-dev: 101.6 and 73.8 ms.

CPU mode got slower on every CPU target: fv-ml1 cpuset 0-5 went 152 -> 205 ms
with a face, and the no-face frame roughly doubled. That is well outside the
run-to-run spread. The suspected cause (not measured) is per-session ORT
thread pools spinning. Reported to augaman-dev. Neither deployment uses CPU
mode.

On esh-ml1 the dependency layer missed the build cache and the rootfs touched
90% until the v0.1.2 image was removed. fv-ml1's build hit the cache, and the
exported requirements are identical, so the stack README now says to check
disk before building on esh-ml1.

This commit is contained in:

2026-09-27 01:13:01 -07:00

parent 317868dc7e

commit ef64a69e30

4 changed files with 589 additions and 6 deletions

									
										stacks/augaman/.env.example
									
		+1
		-1
	
												View File
												
				@@ -6,7 +6,7 @@

				# compose.yaml. Do not add an env_file.

				# Built locally on esh-ml1 from the release tag (see README "Building").

				IMAGE=augaman:0.1.2

				IMAGE=augaman:0.1.3

				PORT=8040

				HOST_IP=10.0.50.80