BOINC wierdness...

[JC]

Hmmm, just saw something new here...a job on one of my boxes spontaneously preempted itself, and started a job about 10 down in the queue Would it ever go back and finish the preempted job? Or would it just continue from the next job, and leave those 10 jobs to get stale in the queue?


????

 

[networkman]

I take you're running for than one Boinc project, yes? I've only ever seen pre-empted units on my sole rig that does both E@H and Rosetta.. and it always gets back to the pre-empted unit to finish it up. I have my resources set at roughly 70/30 in favor of E@H.

It's not uncommon though(at least to me) to see the program jump around in the cache a bit to different workunits, even several days apart.

 

[JC]

No, I run all Rosetta. So far (100k credits) I've seen jobs get preempted, but it always just went to the next job in the queue.

 

[BlackMountainCow]

Check the deadline of the two jobs. Does BOINC run a job now that's due eralier? Maybe the eraliest deadline of your whole queue? Check the message logs. Maybe it says something that you computer is overcommited. Or somethinglike earliest daline first.

 

[JC]

There goes another one!

You're right, BMC. "Using earliest-deadline first scheduling because computer is overcommitted".


Mystery solved

 

[BlackMountainCow]

You're welcome!




Sorry for all the typos, just woke up