-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
Better integration with Ray Serve #1821
Conversation
I think this feature fixes the underlying cause for the problem here: ray-project/ray-llm#94 Thanks @FlorianJoncour! |
Yes it seems to be the same issue. I almost went crazy trying to get this to work before diving into the vllm code |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks good to me, though I would say that the rename is unnecessary :)
One important thing to note is this doesn't actually provide a hard boundary on the process memory usage, so using fractional GPUs doesn't have a 100% guarantee that OOMs will be avoided. That being said, they should be quite unlikely thanks to vLLM memory profiling.
@FlorianJoncour @Yard1 It seems this change causes a bug when
I guess this is because |
@WoosukKwon I see. For now we should do:
|
Co-authored-by: FlorianJoncour <florian@zetta-sys.com>
Co-authored-by: FlorianJoncour <florian@zetta-sys.com>
I use several models using Ray Serve outside of Vllm.
Vllm ask for all ressources to Ray, making it impossible to use other models alongside.
So I use the gpu_memory_utilization parameter to limit the gpu ressources requested by the worker, which then allows placement_group_bundles to be used in Ray Serve deployments.
The RayWorker class has also been renamed to RayWorkerVllm to avoid ambiguities with other Ray actors.
Edit: Clarification, Vllm don't use all Vram, but requests for all ressources to Ray.