Skip to content
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

[Misc] Update instance info of engine in a timely manner #17

Merged
merged 8 commits into from
Aug 27, 2024

Conversation

s5u13b
Copy link
Contributor

@s5u13b s5u13b commented Aug 27, 2024

Previously, we updated the instance info of the engine after each step. Instance info is used by the global scheduler to get the instance's memory usage, etc. However, the actual time point of instance memory update occurs when the scheduler schedules the requests before each step. So, instead of updating the instance info after each step, this pr implements the scheduler to call back the engine to update instance info right after scheduling requests. With this change, the global scheduler can get more timely instance info, which could benefit dynamic scheduling.
Also, I fix some arguments description and TODOs passingly in this pr.

@s5u13b s5u13b requested review from ZeldaHuang and zhypku August 27, 2024 03:15
@s5u13b s5u13b merged commit 56c0c3c into main Aug 27, 2024
4 checks passed
@s5u13b s5u13b deleted the update-instance-info branch August 27, 2024 09:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants