Skip to content

Commit 2967e5e

Browse files
authored
[Benchmark] Correctly kill vllm process in performance benchamrk (#2782)
### What this PR does / why we need it? vLLM now names the process with VLLM prefix after vllm-project/vllm#21445, we should kill the correct process name after one iteration benchmark to avoid OOM issue ### Does this PR introduce _any_ user-facing change? ### How was this patch tested? - vLLM version: v0.10.1.1 - vLLM main: vllm-project/vllm@e599e2c --------- Signed-off-by: wangli <wangli858794774@gmail.com>
1 parent a746f82 commit 2967e5e

File tree

2 files changed

+5
-2
lines changed

2 files changed

+5
-2
lines changed

benchmarks/scripts/run-performance-benchmarks.sh

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -78,7 +78,9 @@ kill_npu_processes() {
7878
ps -aux
7979
lsof -t -i:8000 | xargs -r kill -9
8080
pgrep python3 | xargs -r kill -9
81-
81+
# vLLM now names the process with VLLM prefix after https://github.com/vllm-project/vllm/pull/21445
82+
pgrep VLLM | xargs -r kill -9
83+
8284
sleep 4
8385
rm -rf ~/.config/vllm
8486

benchmarks/tests/serving-tests.json

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -23,7 +23,8 @@
2323
"hf_split": "train",
2424
"endpoint": "/v1/chat/completions",
2525
"dataset_path": "lmarena-ai/vision-arena-bench-v0.1",
26-
"num_prompts": 200
26+
"num_prompts": 200,
27+
"no_stream": ""
2728
}
2829
},
2930
{

0 commit comments

Comments
 (0)