-
-
Notifications
You must be signed in to change notification settings - Fork 10.8k
Fix get_max_num_running_seqs for waiting and swapped seq groups #1068
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
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.
LGTM, thanks!
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.
Left minor comments.
| # that are not finished yet. | ||
| return self.num_unfinished_seqs() |
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 semantic of the function will change because this also counts swapped sequences. Is this expected?
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.
This is intended. get_max_num_running_seqs is being called for a swapped sequence when the swapped sequence is about to be swapped back to the running queue. This means these swapped sequences will soon become running sequences. This is the same logic as waiting sequences.
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.
LGTM
### What this PR does / why we need it? Adjust concurrency group for each npu workflow - for pd and benchmarks share the static-08-01, so only one job can runs on - other job one PR/schedule should have only 1 job runs ### Does this PR introduce _any_ user-facing change? No ### How was this patch tested? CI passed Signed-off-by: Yikun Jiang <yikunkero@gmail.com>
This is the actual correct fix for the issues in #1034.
cc @Yard1