sig666 wrote:

~misfit~ wrote:

sig666 wrote:

~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. --
~misfit~ (Who's *really* looking forward to a 'hardware injection'
arriving soon that'll bump up the electricity bill but will double
WU throughput).

I got 7 work units today (7/16/04) and the to completeion seems to
be fixed.

Yep, it's all looking good now. (Fingers crossed).

*However* (there's always an 'however) I've just set up a Tualatin
Celeron
1.4Ghz and, after the benchmarks (BOINC 3.20) it estimates TC times
of 4hrs 30mins but in actual fact the few WUs it's done so far have
been around 8 hours. *Sigh* It's difficult jugging different
machines using the same set of preferences for optimal throughput.
--
~misfit~

Well I just got another 9 work units. And they are back to 24:40:48.
Geesh! Go figure!

Yeah, spoke too soon. I just got another three X6 units showing 18:24:46
instead of 3:04:07. Shoulda crossed my toes too.
--
~misfit~