feat(vllm): Tackle out of memory errors (EAI-8058) - #251
Open
r0x0r wants to merge 1 commit into
Open
Conversation
…e documentation Signed-off-by: Roman Sirokov <roman.sirokov@amd.com>
r0x0r
force-pushed
the
gpu-out-of-memory
branch
from
August 14, 2026 06:44
be4861d to
3101e06
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This pull request improves GPU selection and user guidance for ROCm and vLLM, especially in shared or containerized environments where the standard
amd-smitool may not be available. It adds a fallback for GPU VRAM telemetry, enhances user warnings and hints for out-of-memory (OOM) conditions, and ensures consistent messaging across CLI and engine surfaces. The changes also include comprehensive tests for the new logic.GPU selection and VRAM telemetry improvements:
/sys/class/drm/card*/device/mem_info_vram_{total,used}) whenamd-smiis not available, so--gpu autoand low-VRAM warnings work reliably in stripped-down containers and shared nodes. The device count for selection now also derives from these sysfs rows ifamd-smiis missing. [1] [2] [3] [4]User guidance and warnings for vLLM:
VLLM_GPU_MEMORY_UTILIZATION_HINTfor the recommended workaround when running out of memory on a shared/busy GPU, ensuring CLI and engine logs use consistent wording.--gpu-memory-utilizationworkaround when vLLM is selected and the GPU is busy, both interactively and in the deployment summary. [1] [2] [3] [4] [5]Documentation:
docs/vllm.mdto explain the behavior on shared/busy GPUs, the fallback telemetry, and the recommended OOM workaround.These improvements make GPU selection more robust in diverse environments and provide clear, actionable guidance to users encountering memory issues with vLLM.