zampp2 GPU capabilities stuck on raw /dev detection — GPU_COUNT env override blocks nvidia-smi enrichment #108
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Fixed in
04ce096.GPU_COUNToverride now merges with the nvidia-smi cache when present, so the model / memory / driver version still flow through for the overridden indexes instead of being discarded.zgaetano referenced this issue2026-05-26 18:22:17 -04:00
zgaetano referenced this issue2026-05-26 18:22:49 -04:00
Fix Plan — #108 GPU_COUNT env override blocks nvidia-smi enrichment
Root cause:
node-agent/index.js:269-284— zampp2.env.workersetsGPU_COUNT=1. Override path pushes raw{device, type, index}triples — nevernameormemory_mb. The_gpuCachefromprobeGpusViaSmi()("NVIDIA L4", 23028 MB) is discarded whenGPU_COUNTset.Fix: Always prefer nvidia-smi enrichment when available. Use override only as fallback count:
On zampp2: remove
GPU_COUNT=1from.env.workeronce cache works.Files:
services/node-agent/index.js:269-284Effort: ~1h
**Priority: P2 — blocks GPU-aware scheduling