Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Doc]: Performance/Optimization Page doesn't mention Pipeline Parallel Size #12012

Closed
1 task done
strangiato opened this issue Jan 13, 2025 · 0 comments · Fixed by #14059
Closed
1 task done

[Doc]: Performance/Optimization Page doesn't mention Pipeline Parallel Size #12012

strangiato opened this issue Jan 13, 2025 · 0 comments · Fixed by #14059
Labels
documentation Improvements or additions to documentation

Comments

@strangiato
Copy link

📚 The doc issue

In the Page
https://github.com/vllm-project/vllm/blob/main/docs/source/performance/optimization.md

One of the recommended options includes the following:

Increase tensor_parallel_size. This approach shards model weights, so each GPU has more memory available for KV cache.

This document does not mention increasing pipeline_parallel_size which would also result in the model being sharded across more GPUs so their is more memory available for KV cache.

Suggest a potential alternative/fix

Increase tensor_parallel_size or pipeline_parallel_size (if using Multi-Node Multi-GPU). This approach shards model weights, so each GPU has more memory available for KV cache.

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.
@strangiato strangiato added the documentation Improvements or additions to documentation label Jan 13, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant