When Rosetta active, only one GPU active

[Polaxis]

Hi

I just observed, that when Rosetta fills all my cores and threads, only one of my GPUs is active.
Other projects leave enough CPU overhead allowing both GPUs to be active.

Can someone point me to the specific setting that may undo this bottlenecking?

Best regards and thanks in advance

[Dingo]

found this on the Rosetta forum, an answer to the same problem. 

The Percentage of CPU time used for graphics only affects the amount of CPU used on the screensaver so I do not think it will help.  There version of the web site is very old and does not have the more up to date prefeeences that other projects have to reduce CPU etc.  I think you might be Euchred.  Given the number of tasks that the project sends out it might not be a problem.

Setting "Use at most 90% of the CPUs" is a legitimate change if you think it might help (I have no idea).
"Use at most 90% of CPU time" does more harm than good in my experience. Rosetta works best with this always set to 100%
"at most 90% of CPU time" is implemented by running 100% for 90% of the time, then 0% for 10% of the time and rapidly switching between the two, not at 90% for 100% of the time as you might more reasonably expect.

You might want to try reducing the %age of CPUs used a little further to see if it makes any difference, though I can't see why it would when Rosetta never calls for any gpu time.

[Polaxis]

found this on the Rosetta forum, an answer to the same problem. 

The Percentage of CPU time used for graphics only affects the amount of CPU used on the screensaver so I do not think it will help.  There version of the web site is very old and does not have the more up to date prefeeences that other projects have to reduce CPU etc.  I think you might be Euchred.  Given the number of tasks that the project sends out it might not be a problem.

That was actually me asking the same question in the Rosetta forum 
Unfortunately it is still random.
My best guess is:
BOINC scheduler.

It checks all the tasks and due date and prioritizes CPU tasks (+1 Core due minus 1 GPU that has to be "served").
As far as I know, nothing that I can automate easily to prevent it, or can I?

Setting "Use at most 90% of the CPUs" is a legitimate change if you think it might help (I have no idea).
"Use at most 90% of CPU time" does more harm than good in my experience. Rosetta works best with this always set to 100%
"at most 90% of CPU time" is implemented by running 100% for 90% of the time, then 0% for 10% of the time and rapidly switching between the two, not at 90% for 100% of the time as you might more reasonably expect.

You might want to try reducing the %age of CPUs used a little further to see if it makes any difference, though I can't see why it would when Rosetta never calls for any gpu time.