No more tasks that went in high priority mode!

High Priority mode is not a problem, it is your friend.

BOINC normally does work in the order it was downloaded. If that meets all deadlines, that's great.

If BOINC isn't 100% sure it can easily meet all deadlines, it will do any work that is at-risk first.

The only lesson I can bring from "high priority" mode is that BOINC should be more secretive about what it's doing. If BOINC did "high priority" but didn't tell people, they would not be upset about something that isn't an issue.

---

I understand how High Priority works, however it should work when WU's are in danger of exceeding the deadline not just kick in and empty the cache. None of my WU's were close to going over the deadline but it emptied it anyway. I've been doing this for a while and I've had things happen that created client errors and dumped all my cache but it built back up fairly quickly after it started reporting good WU's. No such thing this time.

---

http://www.teamstarfire.org/

I understand how High Priority works, however it should work when WU's are in danger of exceeding the deadline not just kick in and empty the cache. None of my WU's were close to going over the deadline but it emptied it anyway. I've been doing this for a while and I've had things happen that created client errors and dumped all my cache but it built back up fairly quickly after it started reporting good WU's. No such thing this time.

I'm not so sure.

BOINC does not do things randomly. It does not randomly decide that work needs to be done "high priority" and the sheer amount of fear of anything that might be anything other than exactly what one expects really gets in the way of diagnosing the problem.

Forget about "it's High Priority" and ask instead "Why does BOINC think there is a deadline issue?"

For one cruncher, his "% time BOINC can do work" was 0.005% -- and that means that BOINC thinks it can only crunch about 4.3 seconds per day. A one-hour WU takes more than 800 days if you only get 4.3 seconds per day.

"High Priority" was not the problem, the active time was the problem.

Most of these issues that have been tracked down have been tracked to someone accidentally setting the system clock -- usually because they were using the Windows clock as a calendar and clicked where they should not have.

I know, because I've done that.

If time suddenly jumps, then DCF and active fraction and all of those metrics can get really badly messed up.

It's easily fixed by stopping BOINC, finding the offending values in CLIENT_STATE.XML, and putting something more reasonable in place of the goofy numbers. I'd probably put in 0.5 being conservative, but 1.0 is probably okay.

---

I've checked the system time and I know that I didn't change it and back again. I've also compared CLIENT_STATE.XML to another computer and there is no discernible difference in times. I think I'll uninstall and reinstall it and see if that will help.

---

http://www.teamstarfire.org/

Something was definitely wrong with the date. In the Statistics tab it had Jun 09 then Dec 10 then Mar 11 and so on. I completely uninstalled it and reinstalled and it's starting to fill the cache now.

---

http://www.teamstarfire.org/