How I can force BOINC to process all downloaded WUs in the same time, not only two of them?

---

You can not.

---

Semper Eadem
So long Paul, it has been a hell of a ride.

Park your ego's, fire up the computers, Science YES, Credits No.

Add more CPUs ;-)

It actually would not make sense to process more than one BOINC client tasks on one CPU (or one virtual CPU on HT systems), they would be slower than handling them one by one.

> You can not.
>
Well, you can, sort of; but it's a bad/very wasteful idea. What you do is that you take your "URL Project" and put it into, "Attach to Project" along with your account project ID#. Here's why it's a bad ideal. You will see to WU in BOINC crunching away...., but never at the same time. While BOINC is working on one WU, the other WU is "Paused" for a certain amount of time, then it takes time to stop work on the one WU and resume the other WU that was paused. If you look at the finished time it took to complete each work unit, the time indicated that it to complete is NOT real, because it does not take into account time-paused, time-stop-to-swith back and forth between WU. The end result may be that it actually, on average, take longer to complete WUs and return for new ones.

---

> > You can not.
> >
> Well, you can, sort of; but it's a bad/very wasteful idea. What you do is
> that you take your "URL Project" and put it into, "Attach to Project" along
> with your account project ID#. Here's why it's a bad ideal. You will see to
> WU in BOINC crunching away...., but never at the same time. While BOINC is
> working on one WU, the other WU is "Paused" for a certain amount of time, then
> it takes time to stop work on the one WU and resume the other WU that was
> paused. If you look at the finished time it took to complete each work unit,
> the time indicated that it to complete is NOT real, because it does not take
> into account time-paused, time-stop-to-swith back and forth between WU. The
> end result may be that it actually, on average, take longer to complete WUs
> and return for new ones.
>

This (the CPU counter keeps going when swapped out) is only true for Win9x based machines

NT/W2k/Xp all time slice quite nicely, and DO report actual amount of CPU time used.

---