I'm experiencing something odd with 7.0.64 going into high priority mode with some WCG CPU tasks due in 6.1 days (it started when they had 8 days). When I set the cache levels to a minimum work buffer of 6 days and a max additional of .01 days, BOINC goes into high priority mode for the tasks with 6 day deadlines. If I drop the minimum to 5 days, they revert to normal procesing. It is not a WCG problem - I tested yesterday with some SETI CPU tasks with 10 day deadlines and got the same result. When I raised the minimum work buffer to 10 days, they started in EDF mode. I lowered it to 6 days and they revert to normal running.

I don't think I have too much cpu work on hand - less than 1 day of WCG CPU tasks and 6 days of SETI CPU tasks. If that's too much, why would lowering the cache setting impact the EDF decision?

Is that cache setting supposed to be a factor in determining EDF mode? Or is this a holdover in the logic from 6.12 when the first cache setting had a different meaning? I've forgotten the definition but it was something similar to "connect every x days". In other words, is BOINC going EDF because it thinks I won't connect for the number of days in my minimum work buffer setting? My activity menu settings are to run and connect always.

---

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

Is that cache setting supposed to be a factor in determining EDF mode? Or is this a holdover in the logic from 6.12 when the first cache setting had a different meaning? I've forgotten the definition but it was something similar to "connect every x days". In other words, is BOINC going EDF because it thinks I won't connect for the number of days in my minimum work buffer setting? My activity menu settings are to run and connect always.

Yes.

Is that cache setting supposed to be a factor in determining EDF mode? Or is this a holdover in the logic from 6.12 when the first cache setting had a different meaning? I've forgotten the definition but it was something similar to "connect every x days". In other words, is BOINC going EDF because it thinks I won't connect for the number of days in my minimum work buffer setting? My activity menu settings are to run and connect always.

Yes.

Thanks for the confirmation, Richard. I had thought that the deadline and the amount of work on hand were the factors. It is just a nuisance item - I use a max concurrent setting to keep WCG from using all cores. I'll be finished with this oversized batch of tasks tonight and don't usually run into deadline issues. If it is a known problem, will let it ride.

---

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