Oh yes...I can say this problem did not begin until I put in a video card with a GPU that could be used by BOINC so I would imagine the problem is rooted there.
I actually brought this issue up on the S@H board and according to many people there it is a known problem and has been for some time.
Your problem is most likely that you use BOTH your cpu and your gpu on the same project!! Boinc, the software, currently has no clue how to separate the needs of one versus the other. The gpu is crunching thru units at the rate of 10 per hour while the cpu is going thru units at the rate of 1 every 3 hours, all numbers are made up by me, so when you need workunits Boinc gets workunits, sometimes LOTS of workunits because after all your gpu needs them! The best thing is to chose one to crunch here and move the other to another project. There are Beta version of the Boinc software but I do not know if any of them are any better at this yet.
It's not actually as easy as that.
BOINC, such as the currently recommended v6.10.58, measures the size of your CPU queue and your GPU/CUDA queue separately, and requests the right amount of work (measured in seconds) to keep each queue topped up, independently. And the Einstein project, in particular, is good at estimating the relative speeds of your CPU and your GPU, and describing the "size" of each task and the speed of each device appropriately, so that the wild fluctuations in DCF seen on some projects when running both types of device don't happen here (or at least not so much - BOINC can still be confused by, for example, multiple graphics cards of different speeds). The newer BOINC clients, such as the v6.12.13 in final testing, are better still, but v6.10.58 isn't bad.
My new host 3868392 is running both CPU and GPU Einstein tasks, without any of the side effects you describe - but without providing any evidence of a work fetch problem into my debug log, either.
Thanks for the update Richard, another thing I learned today!!
To the uninitiated, the problem appears as if it might be caused by an inconsistency in classification of the different tasks. What I observed, until I managed to disable CPU tasks, was that BOINC would request CPU and GPU tasks from Einstein after completing a CUDA task, regardless of the number of CPU-only work that was queued. Einstein would then usually send a CUDA task and another CPU-only task, which would take about four times as long as the task that just completed.
If my guess is correct, either BOINC needs to ask for only GPU work when CUDA jobs are required or Einstein needs to ignore requests for CPU work when both CPU and GPU are requested from BOINC.
RE: RE: RE: Oh yes...I
)
Thanks for the update Richard, another thing I learned today!!
To the uninitiated, the
)
To the uninitiated, the problem appears as if it might be caused by an inconsistency in classification of the different tasks. What I observed, until I managed to disable CPU tasks, was that BOINC would request CPU and GPU tasks from Einstein after completing a CUDA task, regardless of the number of CPU-only work that was queued. Einstein would then usually send a CUDA task and another CPU-only task, which would take about four times as long as the task that just completed.
If my guess is correct, either BOINC needs to ask for only GPU work when CUDA jobs are required or Einstein needs to ignore requests for CPU work when both CPU and GPU are requested from BOINC.