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

Would RPyC be a good alternative of Ray? #908

Closed
LinPoly opened this issue Aug 30, 2023 · 1 comment
Closed

Would RPyC be a good alternative of Ray? #908

LinPoly opened this issue Aug 30, 2023 · 1 comment

Comments

@LinPoly
Copy link

LinPoly commented Aug 30, 2023

Hi vLLM developers @WoosukKwon @zhuohan123 . I noticed that there is a plan to find alternative frameworks for distributed inference in the RoadMap. I think RPyC maybe a good option for single machine scenario. RPyC is a concise RPC framework with basically no extra dependencies and its APIs are quite handy. RPyC is adopted by lightllm, a project parallel with vLLM, as its distributed backend and this is how it uses RPyC.

As mentioned in some issues, Ray will bring heavy overhead for single machine serving. RPyC maybe a lightweight alternative to it. If you are interested, I think I can help to add RPyC support, create a new PR and implement it.

@seanshi-scale
Copy link

seanshi-scale commented Oct 11, 2023

I tried substituting Ray with RPyC at #1318, but wasn't able to get better performance. There's certainly more things that one could do to speed up RPyC, I don't really have time to work on it though. I feel like there's a few quirks with RPyC that makes this slower, e.g. the API it provides to send python objects over between processes and some tcp_nodelay setting that I had to patch in/expose.

I think if people have the time, it still could be worth looking into though.

@hmellor hmellor closed this as not planned Won't fix, can't repro, duplicate, stale Mar 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants