Man, this Duron crunches quick!

[TerryMathews]

It's running at 7x143MHz with 256MB of RAM at CAS2. The avg. WU time is down 20 mins, to 6:40, and it hasn't done as many now as it did before yet.

Some of the WUs have been 4:15 or so, but I think they're the weird ones that are really easy to crunch. The total avg. of new WUs seems to be just under 6 hours.

Now if I can just find a T-Bird that will run even faster. I'm thinking my next proc will be... something that can handle 11x143 or 1.573GHz.

 

[toft-dk]

Thats really fast for a Duron, what kinda Cooler are you using. and at what temps ?







<< something that can handle 11x143 or 1.573GHz >>

That would be a 1400/266 mhz Athlon i would think
I've heard a lot of them would hit that mark, with proper cooling

 

[TerryMathews]

It's a Duron 750 @ 1.85V, with a Titan Majestic V orb-ripoff cooler. It hovers about 45-50 deg. C. I've got my personal proxy grabbing the "interesting" work units, so it's possible that this is just the good WUs, but I think that there is a significant speed boost too.

 

[DarkMajiq]

Wow, I envy, you I used to run my 900 T-Bird at that speed, but I've had to knock the FSB down 1MHz for stability, now I'm just under the 1GHz mark

 

[Assimilator1]

Wow! ,that is fast for a Duron
Nice times

 

[Sukhoi]

Fast times!

 

[ElFenix]

i love speed!

 

[TerryMathews]

According to SetiQueue, my avg WU time is down to 6:31, from 7:something. It's still going down a few minutes each WU...

 

[DarkMajiq]

Wow, do I take it you don't use this machine much?

 

[TerryMathews]

Well... SetiQueue reports two numbers: average time and average CPU time. In theory, if I never used my machine, it would do WUs in 6:31. However, I do a lot on this machine and along with the Win2k overhead the average time is actually 14:59.

If only I had a spare 1.5GHz machine laying around to do Seti 24/7 without any interference on my part...

 

[ColinP]

Your not the Terry Matthews who founded Newbridge are you ???



Col

 

[TerryMathews]

avg time is down to 14:10 and avg cpu time is 6:28

 

[Sukhoi]

That's really way too big of a gap between the two times unless you do a ton of stuff on your computer. What are the actual WU times that are being logged in SETI Driver or SETIQ or whatever? 14 hours is too long.

 

[Assimilator1]

cpu time shown in History or results is the main 1 to look at

This is the overall average cpu time
644) Terry Mathews 64 509 hr 39 min 7 hr 57 min 48.5 sec

Maybe the SETIQ av cpu time is high because of earlier slower WU's?

 

[TerryMathews]

I don't know, but both computers at my house that are running SETI@Home through my SetiQueue server are reporting a few hours per WU disparity between avg and avg cpu. It could be several things... I've not been running SETI that long, maybe all the stats aren't right. The SetiQueue is running on a AMD 5x86 100, maybe it doesn't like 486s too well... I had some problems with the SetiQueue last night, maybe messing around with the box threw the stats off. ???

The other box does nothing, except my girlfriend uses IE about once a day for less that 30 mins. It's running Win98SE with no background tasks except Seti. Not even disk defrag.