[PD] Add retry interval in ensure_prefill_info#20832
Conversation
Signed-off-by: Shangming Cai <csmthu@gmail.com>
Summary of ChangesHello, 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 enhances the robustness of the prefill information ensuring process within the disaggregation decode component. By introducing a time-based retry interval, the system avoids aggressive, immediate re-attempts for failed prefill operations, allowing for better handling of temporary network or resource issues. This change prevents a large number of retries from occurring within a very short timeframe, making the retry logic more effective and less resource-intensive. Highlights
🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console. 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. Footnotes
|
|
/rerun-stage stage-c-test-8-gpu-h20 |
|
✅ Triggered |
There was a problem hiding this comment.
Code Review
This pull request introduces a retry interval to the ensure_prefill_info function, which is a good improvement to prevent rapid-fire retries in a non-blocking scenario. The changes are logical and correctly implement the intended delay using time.monotonic. My feedback focuses on minor code style improvements to make the cleanup logic more concise and robust.
Signed-off-by: Shangming Cai <csmthu@gmail.com>
Signed-off-by: Shangming Cai <csmthu@gmail.com>
Signed-off-by: Shangming Cai <csmthu@gmail.com>
Signed-off-by: Shangming Cai <csmthu@gmail.com>
Signed-off-by: Shangming Cai <csmthu@gmail.com>

Motivation
A following PR to #20785
_max_ensure_retrieswould be meaningless for production since 30 retries all fail within 1 second.Modifications
Accuracy Tests
Benchmarking and Profiling
Checklist
Review Process
/tag-run-ci-label,/rerun-failed-ci,/tag-and-rerun-ci