After running BOINC 7 for a couple of months, I have to make one comment on the new design.

I don't like it.

I am subscribed to 7 projects, including Cosmology@Home. My machine has 4 CPU cores and runs 32 bit Windows.

The previous version of BOINC would keep a workunit inventory for most of the projects. I would usually run one Cosmology and 3 workunits from other projects. This worked fine.

The new BOINC tends to download a large batch of workunits for one project and run nothing only that one project until the batch is done. Cosmology work units are huge and one cannot reasonably run 4 Cosmology work units at one time on a 32 bit system. They take too much memory.

So everything works fine, except when the scheduler gets its large batch of Cosmology. For the next few days my machine is very slow doing anything else.

I liked the old way better.

---

After running BOINC 7 for a couple of months, I have to make one comment on the new design.

I don't like it.

I am subscribed to 7 projects, including Cosmology@Home. My machine has 4 CPU cores and runs 32 bit Windows.

The previous version of BOINC would keep a workunit inventory for most of the projects. I would usually run one Cosmology and 3 workunits from other projects. This worked fine.

The new BOINC tends to download a large batch of workunits for one project and run nothing only that one project until the batch is done. Cosmology work units are huge and one cannot reasonably run 4 Cosmology work units at one time on a 32 bit system. They take too much memory.

So everything works fine, except when the scheduler gets its large batch of Cosmology. For the next few days my machine is very slow doing anything else.

I liked the old way better.

+1
Alexander

From the BoincFAQ Boinc 7 page:

In finer detail
The CPU and GPU schedulers have been rewritten from the ground up, as is the new work fetch module. This means that work fetch will happen completely different from how you're used to it in BOINC 6. Where BOINC 6 would for instance report work and immediately ask a new task, BOINC 7.0 will try to store a couple of "ready to report" results, report them and immediately request work only when BOINC is under the value set by the Minimum work buffer.

This means that when you have left your old BOINC 6 values for "Connect to" + "Additional work" at, example given 0.1 and 1.0, that BOINC 7.0 will ask for 1.1 days worth of work and ONLY renew this cache when it's fallen under the 0.1 days worth of work limit.

Which means that it can happen that your BOINC runs empty, because 7.0 won't request new work before it has dropped below the 'minimum work' setting and will only ask for work up to the 'and additional' setting --and that only from the project that has the highest priority (worst REC to resource share ratio). Only if that project doesn't have work it will ask other projects in order of priority.

This is easily fixed though, by turning the values around. Where the old values were 0.1 + 1.0, you now go for Minimum work buffer 1.0 + Maximum additional work buffer 0.1

Claggy