Weird Scheduling -- I think
16 Dec 2010 20:19:21 UTC
Topic 195514
(moderation:
Hi,
Kinda new to this so this may be just the way it works. I've noticed a change in a) the work amount given out and 2) the way the tasks are executed.
a) Up until about a week ago, my task count hovered around 6 - 8 at any given time; some executing others waiting to execute. Just recently, I've had two batches downloaded of over 100 tasks as viewed in the "Tasks" tab.
b) My executing tasks seem to jump around now. It will work on a task, then suddenly suspend that task and start a brand new one. If I restart the computer it will pick a new, unstarted task to work on. It used to pick up where it left off.
My question, is this the expected behavoir?
Thanks,
Bob
Weird Scheduling -- I think
)
Hi,
a lot of people have the same problem. See here http://einsteinathome.org/node/195489.
It´s maybe linked to your CUDA nvidia graphics card.
Thanks. I'll try setting the
)
Thanks. I'll try setting the GPU to no. I did notice that I started getting GPU tasks suddenly after Windoz updated something.
Thanks,
Bob
That did it. Thanks for the
)
That did it. Thanks for the help!
RE: That did it. Thanks for
)
Do you crunch elsewhere with your gpu now then?
Not sure what you mean. I
)
Not sure what you mean. I just turned off the GPU setting in Einstien@home preferences. I did this because I saw elsewhere on the boards that this stopped the jumping around rather than completing tasks.
I think mikey wanted to know
)
I think mikey wanted to know if you have attached to another (additional) project with a CUDA application to keep your GPU busy.
Gruß,
Gundolf
Computer sind nicht alles im Leben. (Kleiner Scherz)
RE: I think mikey wanted to
)
That is it exactly, thanks for putting it into words people can understand! Sometimes I know what I want to say, it just doesn't come out.
Boinc has long had a problem with both the cpu and the gpu crunching for the same project due to their wildly different work fetch rules. The cpu will bounce around from unit to unit trying to return the unit expiring the soonest if it becomes worried about the deadlines. The gpu on the other hand works on a fifo, or first in first out, basis. Meaning the first gpu unit downloaded is the first gpu unit crunched, the second unit downloaded is the second unit crunched, etc. This can cause issues with long term debt etc for a project, so it was suggested a while back that users not crunch for a single project using both the cpu and gpu, but instead to split them up onto different projects. I know Boinc has gone thru many versions since this was suggested but it is still my practice, and when I recently tried putting both on the same project, Boinc went wonky! This was when the project had plenty of cpu and gpu units, so is not related to the current problems.
RE: RE: I think mikey
)
FYI, the GPU FIFO issue has been addressed in the latest development test builds, and v6.12.8 (Windows/Linux) / v6.12.9 (Mac) seem to be working well in this respect.
RE: RE: RE: I think
)
Oooh, Ohhh that is what I have been waiting for, THANKS!!!
Many thanks to all for the
)
Many thanks to all for the help and info. I'm running only one project, Einstien@home. One day I may look into something else when I have time.
Thanks.