-
Notifications
You must be signed in to change notification settings - Fork 20
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
Add ability to take one GPU out of action (with immediate effect) #135
Comments
Yes, it should stop immediately but you have to save the settings by clicking the "Save" button. |
Does this work correctly with v8.1.17? |
I hadn't realised there was a new version out. That has fixed the problem! (Sorry if you read the opposite just now, I thought I was in the other discussion, then edited this to correct it). I did notice when I upgraded one of the machines (the one I view them from), it warned me the others were out of date. Is that a new feature? And will it work if it's own client is out of date? |
All machines need to be updated for the fix to work. |
What I meant in the second paragraph was, in future, when the next version is released, if none of the machines have the new version, will I be informed in the version column? Or does one machine have to have been updated so it spots the difference? |
No updates needed to see the version difference between the latest. |
I run Boinc aswell, and sometimes would like to switch a GPU out of use for Folding. For example, I had received a World Community Grid Boinc task (they're rare on GPU) and was trying to switch off the GPU which was trying to do both at once. I disabled a GPU (1 of 5 GPUs), and nothing happened, they all kept running, but in issue 115 you told me that would pause the work unit. Although I wasn't trying to pause the task, I wanted it to continue on another GPU when another task finished. I assume when that particular GPU finished the task, it would stop, but I wanted it immediate, mainly so I could tell I had the right GPU!
The text was updated successfully, but these errors were encountered: