You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Both commands succeed when running separately, consuming approximately 75% and 20% of the vRAM respectively.
However when you start the 72B first and then 14b. the 14b will refused to start with Exception
ValueError: No available memory for the cache blocks. Try increasing `gpu_memory_utilization` when initializing the engine.
Note that the 14B vllm server outputs the following log
peak_memory would include the other vllm used vram and result in negative available_kv_cache_memory
Before submitting a new issue...
Make sure you already searched for relevant issues, and asked the chatbot living at the bottom right corner of the documentation page, which can answer lots of frequently asked questions.
The text was updated successfully, but these errors were encountered:
#2248 (comment) suggest counting used vRAM before loading model and exclude it when calculating the available_kv_cache_memory. it seems works well when you staggered startup different vLLM worker in the same card
Your current environment
The output of `python collect_env.py`
Model Input Dumps
No response
🐛 Describe the bug
I want to run Qwen2.5-14B-Instruct-GPTQ-Int4 and Qwen2.5-72B-Instruct-GPTQ-Int4 with one 80G A100.
with following command
Both commands succeed when running separately, consuming approximately 75% and 20% of the vRAM respectively.
However when you start the 72B first and then 14b. the 14b will refused to start with Exception
Note that the 14B vllm server outputs the following log
which has negative kv_cache_size.
it looks like currently
vllm/vllm/worker/worker.py
Lines 213 to 219 in 1cfde82
peak_memory would include the other vllm used vram and result in negative available_kv_cache_memory
Before submitting a new issue...
The text was updated successfully, but these errors were encountered: