I upgraded to 5.6.0 from 5.4.9 because of the conflict between SETI Enhanced and SETI Beta. This upgrade fixed the conflict but I noticed a bug in 5.6.0. The client no longer reschedules the cpu's therefore, the time to completion never gets adjusted correctly and not enough work is downloaded. I have 5.6.0 instaled on 5 different machines, all run Windoze XP Pro, and they all are doing the same thing.

I upgraded to 5.6.0 from 5.4.9 because of the conflict between SETI Enhanced and SETI Beta. This upgrade fixed the conflict but I noticed a bug in 5.6.0. The client no longer reschedules the cpu's therefore, the time to completion never gets adjusted correctly and not enough work is downloaded. I have 5.6.0 instaled on 5 different machines, all run Windoze XP Pro, and they all are doing the same thing.

The 5.6.x line does not annouce the reschedule as aggressivly as it used to. It also does not reschedule at the same triggers anymore,it tries to wait for a checkpoint instead.

The work fetch has been improved so that it is less likely to overfill the queue. This is probably why you are getting less work at one time.

---

BOINC WIKI

BOINCing since 2002/12/8

The work fetch has been improved so that it is less likely to overfill the queue. This is probably why you are getting less work at one time.

To state it a bit clearer: My experience is, that if you were assigned to multiple projects, with older Boinc versions you had to experiment with the connection interval until the queue length was somehow like you wanted. Only "somehow", because you often had too much work for projects with a small ressource share and too less for those with high ressource share. With 5.6.x if you want to have a queue length of 2 days you set your connect interval to 2 days and all projects, that are allowed to download by LTD, will have a queue of 2 days plus a fraction of one WU.

Norbert

---