gahow/aituner
0
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Use vllm cu129 wheel on dash0

Browse Source
This commit is contained in:
Gahow Wang
2026-05-02 08:28:23 +08:00
parent e215827503
commit 1880e859b5
3 changed files with 6 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
docs/qwen30b-community-vllm020/harness-early-stop-ablation-20260502.md
View File

@@ -19,9 +19,9 @@ Both specs start from the same base vLLM configuration. The base contains only s
PyPI reports `vllm==0.20.0` as the current community release checked on 2026-05-02. The dash0 runtime venv is on local rootfs rather than CPFS, because installing torch/CUDA wheels into CPFS was I/O-bound:
`/tmp/wjh/venvs/vllm-0.20.0-auto`
`/tmp/wjh/venvs/vllm-0.20.0-cu129`
The first plain `pip install vllm==0.20.0` smoke pulled `torch 2.11.0+cu130` and failed on dash0's driver (`570.133.20`, CUDA 12.9). The active install uses the vLLM-documented `uv pip install vllm==0.20.0 --torch-backend=auto` path so uv selects a CUDA backend compatible with the installed driver.
The first plain `pip install vllm==0.20.0` smoke pulled `torch 2.11.0+cu130` and failed on dash0's driver (`570.133.20`, CUDA 12.9). The active install uses the vLLM 0.20.0 GitHub release `+cu129` wheel and the PyTorch CUDA 12.9 index, matching the vLLM documented CUDA 12.9 install path for this driver.
Install log: