Skip to content

GitLab

"vllm/vscode:/vscode.git/clone" did not exist on "984d18498a420d771c4a38c6e6e3f3aacb090157"
Unverified Commit 228b768d authored by Jennifer Zhao's avatar Jennifer Zhao Committed by GitHub
Browse files

[Doc] Minor v1_user_guide update (#15064) 


Co-authored-by: default avatarRoger Wang <136131678+ywang96@users.noreply.github.com>
parent 027827cc
Hide whitespace changes
Inline Side-by-side
Showing with 2 additions and 0 deletions
docs/source/getting_started/v1_user_guide.md
View file @ 228b768d
...@@ -2,6 +2,8 @@ ...@@ -2,6 +2,8 @@
V1 is now enabled by default for all supported use cases, and we will gradually enable it for every use case we plan to support. Please share any feedback on [GitHub](https://github.com/vllm-project/vllm) or in the [vLLM Slack](https://inviter.co/vllm-slack). V1 is now enabled by default for all supported use cases, and we will gradually enable it for every use case we plan to support. Please share any feedback on [GitHub](https://github.com/vllm-project/vllm) or in the [vLLM Slack](https://inviter.co/vllm-slack).
To disable V1, please set the environment variable as: `VLLM_USE_V1=0`, and send us a GitHub issue sharing the reason!
## Why vLLM V1? ## Why vLLM V1?
vLLM V0 successfully supported a wide range of models and hardware, but as new features were developed independently, the system grew increasingly complex. This complexity made it harder to integrate new capabilities and introduced technical debt, revealing the need for a more streamlined and unified design. vLLM V0 successfully supported a wide range of models and hardware, but as new features were developed independently, the system grew increasingly complex. This complexity made it harder to integrate new capabilities and introduced technical debt, revealing the need for a more streamlined and unified design.
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment