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

Question: utilization_watcher algorithm design #27

Open
Forsworns opened this issue Oct 21, 2024 · 1 comment
Open

Question: utilization_watcher algorithm design #27

Forsworns opened this issue Oct 21, 2024 · 1 comment

Comments

@Forsworns
Copy link

I found that the algorithm you used is much different from the implementation of vcuda-controller. Why g_total_cuda_cores is multiplied by 2 here? And why the original implementation of vcuda is removed, are they not suitable in your case? Hope you can share your experience on the algorithm design, thanks :)

And their utilization_watcher is

https://github.com/tkestack/vcuda-controller/blob/72e0115d5884f22469de857271c002c84c0d0543/src/hijack_call.c#L303

@Forsworns Forsworns changed the title Question: Question: utilization_watcher algorithm design Oct 21, 2024
@AllenXu93
Copy link
Contributor

Same question

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

No branches or pull requests

2 participants