I've notices the CPU is not getting any work at all.
I know the GPU gets work first.

But I set a Buffer for 5 days, no CPU work, but the buffer is filled to 5 days.
Next I dropped the buffer to 2 days. BOINC is requesting CPU work.
Stayed there for a couple of days. The buffer fills to 2 days and stays there.

Now I set the buffer back to 3 days and I immediately get new work.
And a lot of it, of course all GPU.

And what do you see in message log? Does BOINC client asks for CPU work and doesn't get it or it doesn't ask for CPU work?

As you can see, it asks for CPU work only.

I was building an additional in BoincTasks.
If GPU work > 2 day and CPU work < 0.5 day set buffer to 2 days.

That's when I noticed the buffer staying on 2 days for a couple of days and no CPU work except for some AP work.
____________TThrottle Control your temperatures. BoincTasks The best way to view BOINC. Anza Borrego Desert hiking.

I've noticed that 7.0.28 will keep asking for GPU work until it gets to about 1.25 days more than my min + additional setting, and even at that level it will ask for a few thousand seconds of GPU work. I use local preferences of 6 and .01. I don't get much CPU work until it gets to 7.25 days of GPU work per BOINCTasks' sum of estimated times. You can intervene and temporarily turn off GPU fetch in the SETI@Home project preferences (website). I have do this about once a week to rebalance the cache. Of course, that would affect all of your hosts unless you are using venues (home, school, etc).

Does it know how many GPU tasks are running ?????

It seems to respond when I change my count setting.
____________
Another Fred
Support SETI@home when you search the Web with GoodSearch or shop online with GoodShop.

I've noticed that 7.0.28 will keep asking for GPU work until it gets to about 1.25 days more than my min + additional setting, and even at that level it will ask for a few thousand seconds of GPU work. I use local preferences of 6 and .01. I don't get much CPU work until it gets to 7.25 days of GPU work per BOINCTasks' sum of estimated times. You can intervene and temporarily turn off GPU fetch in the SETI@Home project preferences (website). I have do this about once a week to rebalance the cache. Of course, that would affect all of your hosts unless you are using venues (home, school, etc).

That's what I've been trying to automate. That's when you don't get any work at all.
No CPU that way.

But I expect you get no problems if you have one GPU.
____________TThrottle Control your temperatures. BoincTasks The best way to view BOINC. Anza Borrego Desert hiking.

I've noticed that 7.0.28 will keep asking for GPU work until it gets to about 1.25 days more than my min + additional setting, and even at that level it will ask for a few thousand seconds of GPU work. I use local preferences of 6 and .01. I don't get much CPU work until it gets to 7.25 days of GPU work per BOINCTasks' sum of estimated times. You can intervene and temporarily turn off GPU fetch in the SETI@Home project preferences (website). I have do this about once a week to rebalance the cache. Of course, that would affect all of your hosts unless you are using venues (home, school, etc).

That's what I've been trying to automate. That's when you don't get any work at all.
No CPU that way.

But I expect you get no problems if you have one GPU.

Agree my situation is simple with one host and one gpu. The project preference "use NVIDIA (or ATIa) gpu" only tells BOINC to not ask for gpu work. Turning it off will cause BOINC to only ask for cpu work. Definately not an automated approach - hope you find a better way.

____________
Another Fred
Support SETI@home when you search the Web with GoodSearch or shop online with GoodShop.

Agree my situation is simple with one host and one gpu. The project preference "use NVIDIA (or ATIa) gpu" only tells BOINC to not ask for gpu work. Turning it off will cause BOINC to only ask for cpu work. Definately not an automated approach - hope you find a better way.

I tried to automate something like that.
But even though the computer asks for CPU work it gets noting.
Another computer that request in the same period, gets work ever single time.
But just enough to keep the GPU buffer filled.....

Probably there is something wrong with the BOINC scheduler. At least for computers with more GPU's