-
Notifications
You must be signed in to change notification settings - Fork 9
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
2nd GPU WU overallocated CPUs #106
Comments
Can you post logs for this event? |
Strange, I can't tell what is going on here other than for some reason its shutting down the other WU:
According to the log the GPU WU is only assigned 1 CPU, but the UI says 4 and why did it shut down the CPU WU in the first place? This seems to happen every time a new WU is requested, it shuts down existing running ones, except they usually re-start again. |
I found the problem. It will be fixed in the v8.1.12 release. Thanks for the report. |
Glad I could help with something. |
I believe this is fixed. |
If left on default settings with 1 GPU and 4x CPU (its only a 4 core CPU), I had a GPU job start with 1xCPU and in the meantime a CPU job was processing using 3xCPU.
When the GPU job finished, it was assigned a new GPU WU with 4xCPU causing the existing CPU WU to pause with "Resources not available".
Surely the a WU should be chosen based on available resources?
The text was updated successfully, but these errors were encountered: