-
-
Notifications
You must be signed in to change notification settings - Fork 11.7k
[do not merge] V1 scheduler interface #12544
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
Conversation
Signed-off-by: Woosuk Kwon <[email protected]>
Signed-off-by: Woosuk Kwon <[email protected]>
Signed-off-by: Woosuk Kwon <[email protected]>
|
👋 Hi! Thank you for contributing to the vLLM project. Once the PR is approved and ready to go, your PR reviewer(s) can run CI to test the changes comprehensively before merging. To run CI, PR reviewers can do one of these:
🚀 |
|
This pull request has merge conflicts that must be resolved before it can be |
|
@WoosukKwon Any plan to complete this PR? Thanks |
| from vllm.utils import get_exception_traceback, zmq_socket_ctx | ||
| from vllm.v1.core.kv_cache_utils import get_kv_cache_config | ||
| from vllm.v1.core.scheduler import Scheduler | ||
| from vllm.v1.core.scheduler.scheduler import Scheduler |
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.
Is the intent here to also update the engine core to use a configurable type for the scheduler, now that we have an interface for it?
|
Hey @WoosukKwon - I would like to take a look and this PR and see if we can continue working on this. |
|
@GindaChen @joerunde @wangxiyuan Sorry for the delay. I created a new PR #14731. |
No description provided.