-
Notifications
You must be signed in to change notification settings - Fork 501
Improve pdRouter with load-aware routing #1601
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
Summary of ChangesHello @googs1025, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed! This pull request significantly improves the Highlights
Using Gemini Code AssistThe full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips. Invoking Gemini You can request assistance from Gemini at any point by creating a comment using either
Customization To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a Limitations & Feedback Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here. You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension. Footnotes
|
|
TODO: add unit test for this part |
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.
Code Review
This pull request introduces load-aware routing to the pdRouter, which is a great improvement for balancing work between pods. The changes prioritize pod selection based on load metrics before falling back to existing logic. My review identified a critical issue that could lead to a panic due to a potential nil pointer dereference, and a medium-severity issue related to unhandled errors which could make debugging more difficult. I've provided code suggestions to address both of these points.
| } | ||
|
|
||
| // fallback: random selection pods | ||
| decodePod, _ = utils.SelectRandomPod(filteredDecodePods, rand.Intn) |
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.
The error returned by utils.SelectRandomPod is being ignored. If no routable decode pods are available, this function will return nil without logging the underlying reason, making debugging harder. It's better to handle the error, for example by logging it, to provide more context when selection fails.
decodePod, err := utils.SelectRandomPod(filteredDecodePods, rand.Intn)
if err != nil {
klog.ErrorS(err, "failed to select a random decode pod", "prefill_pod", prefillPod.Name)
}806118b to
c1d9727
Compare
|
/cc @varungup90 |
| llmEngine: "sglang", | ||
| expectError: false, | ||
| }, | ||
| { |
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.
add some unit test in improvment part
Signed-off-by: googs1025 <[email protected]>
Signed-off-by: googs1025 <[email protected]>
fb6aa64 to
c3114eb
Compare
|
@varungup90 please for final ack 😄 thanks a lot |
|
/cc @varungup90 |
Pull Request Description
[Please provide a clear and concise description of your changes here]
Related Issues
Resolves: #1600
Important: Before submitting, please complete the description above and review the checklist below.
Contribution Guidelines (Expand for Details)
We appreciate your contribution to aibrix! To ensure a smooth review process and maintain high code quality, please adhere to the following guidelines:
Pull Request Title Format
Your PR title should start with one of these prefixes to indicate the nature of the change:
[Bug]: Corrections to existing functionality[CI]: Changes to build process or CI pipeline[Docs]: Updates or additions to documentation[API]: Modifications to aibrix's API or interface[CLI]: Changes or additions to the Command Line Interface[Misc]: For changes not covered above (use sparingly)Note: For changes spanning multiple categories, use multiple prefixes in order of importance.
Submission Checklist
By submitting this PR, you confirm that you've read these guidelines and your changes align with the project's contribution standards.