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
When specifying VLLM_CPU_OMP_THREADS_BIND it might be better if vLLM did a membind to all or the nodes related to the CPU list rather than just doing it to the node associated with first CPU in the list.
Alternatives
Using numactl and OMP environment variables (i.e. OMP_PLACES, etc...) give better overall control of binding but isn't compatible with CPU tensor parallel partitioning.
Additional context
No response
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:
🚀 The feature, motivation and pitch
When specifying VLLM_CPU_OMP_THREADS_BIND it might be better if vLLM did a membind to all or the nodes related to the CPU list rather than just doing it to the node associated with first CPU in the list.
Alternatives
Using numactl and OMP environment variables (i.e. OMP_PLACES, etc...) give better overall control of binding but isn't compatible with CPU tensor parallel partitioning.
Additional context
No response
Before submitting a new issue...
The text was updated successfully, but these errors were encountered: