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

Add ability to take one GPU out of action (with immediate effect) #135

Closed
hucker75 opened this issue Apr 13, 2023 · 7 comments
Closed

Add ability to take one GPU out of action (with immediate effect) #135

hucker75 opened this issue Apr 13, 2023 · 7 comments

Comments

@hucker75
Copy link

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!

@jcoffland
Copy link
Member

Yes, it should stop immediately but you have to save the settings by clicking the "Save" button.

@hucker75
Copy link
Author

It doesn't stop. I unticked a GPU as shown, then clicked save. They all kept running, both in the web viewer and by watching GPU usage in MSI Afterburner.

image

@jcoffland
Copy link
Member

Does this work correctly with v8.1.17?

@hucker75
Copy link
Author

hucker75 commented Apr 14, 2023

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?

@jcoffland
Copy link
Member

All machines need to be updated for the fix to work.

@hucker75
Copy link
Author

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?

@jcoffland
Copy link
Member

No updates needed to see the version difference between the latest.

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