Adapting Vidur to vLLM and Profiling CPU Overhead
Hi team,
I’m working on adapting Vidur, the LLM inference system simulator, to vLLM. Currently, Vidur’s profiling is based on Sarathi-Serve, but I’d like to explore how to make it compatible with vLLM. From my understanding, simply setting vLLM’s scheduler may not accurately simulate the performance of the latest version of vLLM. Could you provide guidance on how to properly adapt Vidur to vLLM?
Additionally, I noticed that the documentation mentions profiling CPU overhead, but the linked file for this section seems to be missing. Could you clarify how to profile CPU overhead in Vidur or point me to the correct resource?
Any insights or suggestions would be greatly appreciated!
Thanks, Zhaolin Duan
Hi team,
I’m working on adapting Vidur, the LLM inference system simulator, to vLLM. Currently, Vidur’s profiling is based on Sarathi-Serve, but I’d like to explore how to make it compatible with vLLM. From my understanding, simply setting vLLM’s scheduler may not accurately simulate the performance of the latest version of vLLM. Could you provide guidance on how to properly adapt Vidur to vLLM?
Additionally, I noticed that the documentation mentions profiling CPU overhead, but the linked file for this section seems to be missing. Could you clarify how to profile CPU overhead in Vidur or point me to the correct resource?
Any insights or suggestions would be greatly appreciated!
Thanks, Zhaolin Duan
Same issue, did you solve it?
Me too!
Hello @duanzhaol @PhantomKid @manav-aggarwal4 -- We don't plan to officially support vLLM v1 in Vidur. There is some code in the canary branch that you can check out, @nitinkedia7 can share more details about the supported features and limitations. We are working on a new runtime modeling system that would support both vLLM and SGLang.