-
Notifications
You must be signed in to change notification settings - Fork 2.1k
[None][chore] Correct sorting order for attention DP scheduling to prioritize non-relaxed requests #11106
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
|
/bot run --disable-fail-fast |
📝 WalkthroughWalkthroughA sorting order change in the request scheduling function flips how requests are prioritized based on the Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~8 minutes 🚥 Pre-merge checks | ✅ 1 | ❌ 2❌ Failed checks (2 warnings)
✅ Passed checks (1 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing touches
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
/bot run --disable-fail-fast |
|
PR_Github #34151 [ run ] triggered by Bot. Commit: |
|
PR_Github #34151 [ run ] completed with state
|
|
/bot run --disable-fail-fast |
|
PR_Github #34176 [ run ] triggered by Bot. Commit: |
|
PR_Github #34176 [ run ] completed with state |
Fix the sorting order in
schedule_attention_dp_requeststo correctly prioritize non-relaxed requests. The comment states "Prioritize the requests that are not in relax mode", butreverse=Truecauses relaxed requests (get_relax_value=True)to be processed first instead. Removing
reverse=Trueensures non-relaxed requests are scheduled to their target DP rank before slots fill up.Summary by CodeRabbit
✏️ Tip: You can customize this high-level summary in your review settings.