Ilker ManapandClaude Opus 5 d71d785598 Report node memory even when GPU discovery fails ...

Deploying the memory-aware placement showed node01 to node04 reporting 7G
and node05 reporting nothing, on a machine whose /proc/meminfo plainly says
32 GB. node05 has no nvidia-smi, so GPU discovery returns an error, Discover
returns with it, and the memory read — which has nothing to do with cards —
never happened.

That is the node whose memory matters most, because a CPU profile is what a
GPU-less node will be asked to run, and min_memory_gb would have excluded it
from everything.

Read first now, before any path that can return early. The test fails
against the old order.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

2026-09-16 23:50:53 +02:00

..

discover_test.go

Report node memory even when GPU discovery fails

2026-09-16 23:50:53 +02:00

discover.go

Report node memory even when GPU discovery fails

2026-09-16 23:50:53 +02:00

gpu_nonvml.go

Phase 2 (2/2): NVML backend behind a build tag

2026-09-16 02:05:25 +02:00

gpu_nvml.go

Phase 2 (2/2): NVML backend behind a build tag

2026-09-16 02:05:25 +02:00

gpu_smi.go

Phase 2 (1/2): node discovery, engine adapters, process supervisor

2026-09-16 02:01:59 +02:00

gpu_test.go

Phase 2 (1/2): node discovery, engine adapters, process supervisor

2026-09-16 02:01:59 +02:00

gpu.go

Place on nodes that can actually hold the model

2026-09-16 23:12:44 +02:00

ib_test.go

Phase 2 (1/2): node discovery, engine adapters, process supervisor

2026-09-16 02:01:59 +02:00

ib.go

Phase 2 (1/2): node discovery, engine adapters, process supervisor

2026-09-16 02:01:59 +02:00

json_test.go

Phase 2 (1/2): node discovery, engine adapters, process supervisor

2026-09-16 02:01:59 +02:00

memory_test.go

Place on nodes that can actually hold the model

2026-09-16 23:12:44 +02:00

memory.go

Place on nodes that can actually hold the model

2026-09-16 23:12:44 +02:00