~misfit~ wrote:

I just got me some new units and I see that Berkeley still haven't
fixed the X6 problem with the estimated time to completion. The
machine in question (Celeron 600@900) takes less than eight hours per
WU but the units are still showing up as 50 hours in the "To
Completion" column, hence it's only getting one unit at a time.
(Cache set for 1 to 2 days on that one).

Another machine *was* holding around 24 units at a time (Different
preferences) but currently only has seven, four with three hours 'TC'
and three with 18 hours TC.

It's been like this a while, you think they'd have it fixed by now.
It must be creating a lot more traffic for the servers as my machines
are requesting units a lot more frequently than they were before.

Well, I thought it may be fixed but, alas, my latest WU's (eight hours ago)
are of the X6 variety.

The second machine mentioned above has no units with a 3 hour TC (it
actually does them in 2 hours 25 minutes on average), instead it has a cache
of four WU's with an 18+hr TC and one running. It's downloading every 5
hours-odd as each two WUs completed causes the low-water mark to be reached.
I hope the server stays up fine, I only have 12.5 hours of work cached
instead of three days. I don't want to go meddling with my preferences but I
don't want to run out of work either.

I guess this is what they mean by "on the horns of a dillema"?

I hope the benchmaking in the 3.2 client is better. It overestimates the
time on one of my machines by 15% (regardless of what else I'm doing on the
machine) and underestimates on another by over 25%. Makes it hard to
fine-tune the preferences/cache system.

I'm about to close BOINC down and install 3.2 over the top of the previous
version, I hope that's the way to do it and it works smoothly. Wish me luck.
<g>.
--
~misfit~