what is a Seti WU time for Athlon 64

[Ronin]

SetiSpy will help you with that. Just look for it on the web and install it. Make sure in SetiDriver that you check the box that says "Use Seti Spy" so that you can get a log out of it.

 

[SNC]

64 3200 @2200 1gig ram 1:38 min av time over 60 WUs

 

[kamper]

those are getting really close to my p4c2.8, it's running at about 3.1ghz and taking ~3hrs/wu.
so 1:30 effective time

 

[Ronin]

My P4HT 3GHz doesn't do 1:30 WU, even when I'm not running 2 processes... :|

 

[kamper]

well sure, I don't suppose p4s would be anywhere close in a single process competition

anyways my numbers are with a 221 fsb and pretty decent timings, is your 3.0 oc'ed at all Ronin?

 

[CyGoR]

Originally posted by: kamper
those are getting really close to my p4c2.8, it's running at about 3.1ghz and taking ~3hrs/wu.
so 1:30 effective time

You can't say that each wu only takes 1.5hrs... When running one process, it will be close to 2hrs/wu, but really not 1.5hrs.
Although nothing beats a HT PIV with seti, it doesn't get the lowest cpu times..

When reading a result.sah file, how can I see the real cpu time from this line? cpu_time=7876.921875
anything to calculate it with?

 

[mk]

Originally posted by: CyGoR
When reading a result.sah file, how can I see the real cpu time from this line? cpu_time=7876.921875
anything to calculate it with?

CPU time = 7876.921875 seconds (i.e. roughly 2 hours 11 minutes)

 

[CyGoR]

Thanks MK4!
After Seti ends, I will try to pass you with UD

 

[kamper]

Originally posted by: CyGoR

Originally posted by: kamper
those are getting really close to my p4c2.8, it's running at about 3.1ghz and taking ~3hrs/wu.
so 1:30 effective time

You can't say that each wu only takes 1.5hrs... When running one process, it will be close to 2hrs/wu, but really not 1.5hrs.
Although nothing beats a HT PIV with seti, it doesn't get the lowest cpu times..

When reading a result.sah file, how can I see the real cpu time from this line? cpu_time=7876.921875
anything to calculate it with?

I'm well aware of that (see post just above yours). I'm just saying that one wu is put out every 1:30. If you're going to compare total production then it doesn't make sense to use the single wu time for a ht processor. But again, props to amd, because it looks like the newer ones are getting close to p4 production despite only running 1 process at a time.

 

[zodder]

LOL! Yeah, that was supposed to be 2 hours.

Glad to see a few more folks with Athlon64s. I didn't think I'd see that much of a difference going from a Barton 3200+ to the Athlon64, but the integrated memory controller must be smokin'!

 

[Ronin]

Originally posted by: kamper
well sure, I don't suppose p4s would be anywhere close in a single process competition

anyways my numbers are with a 221 fsb and pretty decent timings, is your 3.0 oc'ed at all Ronin?

Dell Dimension XPS :|

 

[kamper]

well, I might be fibbing a bit
whenever I look at seti driver it projects times of about 3:10-3:20, but there are always a few mixed in that take about 2:30. paf's setiQ tells me the average comes to about 3:00 or less, but I think the majority are actually higher