Separate work for GPU and CPU?

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.

This happens with 7.0.28 and 7.0.31.

At 2 days

64836 SETI@home 17-10-2012 09:03 Scheduler request completed: got 0 new tasks
64835 SETI@home 17-10-2012 09:03 Reporting 5 completed tasks, requesting new tasks for CPU
64834 SETI@home 17-10-2012 09:03 Sending scheduler request: Requested by user.

64874 SETI@home 17-10-2012 09:13 Scheduler request completed: got 42 new tasks
64873 SETI@home 17-10-2012 09:13 Requesting new tasks for CPU and NVIDIA
64872 SETI@home 17-10-2012 09:13 Sending scheduler request: Requested by user.


64977 SETI@home 17-10-2012 09:18 Scheduler request completed: got 72 new tasks
64972 SETI@home 17-10-2012 09:18 Reporting 3 completed tasks, requesting new tasks for CPU and NVIDIA
64971 SETI@home 17-10-2012 09:18 Sending scheduler request: To fetch work.

____________
TThrottle Control your temperatures
BoincTasks The best way to view BOINC
Anza Borrego Desert hiking

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 [What number of request in seconds]?
____________
News about SETI opt app releases: https://twitter.com/Raistmer

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?

But I think I see what's going wrong.

Maybe that is....

V7 reused

Connect every
Additional work buffer

->

Minimum work buffer.
Additional work buffer.

So I set the Additional work buffer as in V6, but I probably have to use:

Minimum work buffer in V7.
____________
TThrottle Control your temperatures
BoincTasks The best way to view BOINC
Anza Borrego Desert hiking

After correction that problem in BoincTasks, the results are still the same.

No GPU work.

After changing the buffer from 2 -> 3 I got way over 1000 WU in a singe hour.
All GPU of course.

Now at 3 days.

67320 SETI@home 17-10-2012 10:56 Scheduler request completed: got 0 new tasks
67319 SETI@home 17-10-2012 10:56 Reporting 1 completed tasks, requesting new tasks for CPU
67318 SETI@home 17-10-2012 10:56 Sending scheduler request: Requested by user.

It is getting no CPU work.

The 6.12.33 has plenty of CPU work and gets is regularly.
____________
TThrottle Control your temperatures
BoincTasks The best way to view BOINC
Anza Borrego Desert hiking

Go to preferences, network connections, click 'clear'

Now set "connect every X days" to 4, and additional work buffer to 0.01.

Click update or let it auto report and let me know what happens.
____________


Executive Director GPU Users Group Inc. -
brad@gpuug.org

And set at least the <sched_op_debug> logging flag in cc_config.xml so that you can see exactly what's going on when work is requested/received.

And set at least the <sched_op_debug> logging flag in cc_config.xml so that you can see exactly what's going on when work is requested/received.

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 ?????

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).

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.