Curious about Athlon64 SETI times

[CraigRT]

I haven't had my new PC even long enough to know how fast it completes a work unit, but I was curious as to how fast anyone with an Athlon64 completes a WU.. list relevant information, OS, chipset, CPU rating (obviously), RAM, etc... and obviously how long the work units take on average.

I just got my Athlon64 3200+(512k)/NF3 250GB system setup and it looks like the WU is crunching quicker already over my XP2500+, but it could be psychological!

Curious to see what kind of numbers others are laying down though.

thanks

 

[furie27]

Between 2 and 2 and a half hours with my Athlon 64 3000 system.

 

[Dalephi]

My Athlon 64 3200+ averages 1:51 according to my SetiQueue. Thats after about 1400 WU. Awesome CPU!

 

[CraigRT]

Originally posted by: Dalephi
My Athlon 64 3200+ averages 1:51 according to my SetiQueue. Thats after about 1400 WU. Awesome CPU!

is yours a 1 meg cache or a 512k cache?
mine's a 2.2GHz 512k CPU
looks like about what mine is averaging now too.. we'll see after it does a few (so far only 1)

 

[Dalephi]

Originally posted by: CraigRT

Originally posted by: Dalephi
My Athlon 64 3200+ averages 1:51 according to my SetiQueue. Thats after about 1400 WU. Awesome CPU!

is yours a 1 meg cache or a 512k cache?
mine's a 2.2GHz 512k CPU
looks like about what mine is averaging now too.. we'll see after it does a few (so far only 1)

It is the 1 meg cache.

 

[CyGoR]

The 3200+ is only available at a speed of 2000Mhz with 1MB cache. Unless you've got the mobile version of the CPU, don't know the specs of those..

I've got the 3000+ with 512Kb cache, the only difference with the 3200+.
When I run my CPU @ 2.2Ghz Seti times are also between 1h:50m and 2h:0m.
Default, @ 2Ghz, times are a little over 2hrs. Running WinXP with 1024Mb RAM on a Abit KV8-Max3 (Via).

 

[ken008]

I WANT ONE !

 

[zodder]

I average about 1:45/wu with my A64 3200@2.2.

 

[Markfw]

Originally posted by: CyGoR
The 3200+ is only available at a speed of 2000Mhz with 1MB cache. Unless you've got the mobile version of the CPU, don't know the specs of those..

I've got the 3000+ with 512Kb cache, the only difference with the 3200+.
When I run my CPU @ 2.2Ghz Seti times are also between 1h:50m and 2h:0m.
Default, @ 2Ghz, times are a little over 2hrs. Running WinXP with 1024Mb RAM on a Abit KV8-Max3 (Via).

No, the newcastle core is 2.2 ghz and 512 k cache.

I get about 2 hours under Win2k or XP, and about 1:45 under WinXP64 @2.1 ghz on my 3000+. I haven;t tried on my Opteron setup, as I converted to F@H for my distributed project.

 

[CyGoR]

Well, I've got a Newcastle 3000+ core, and it's running default @ 2.0GHz, although I run it at 2.2GHz

When searching the web, I found this picture which states the same.
Also this Table says the Newcastle core is running @ 2.0GHz

The 3200+ (Clawhammer) also runs @ 2.0GHz, with the only difference of an extra 512Kb cache.

 

[Unforgiven]

all i know is that i got in on one of the amd promo deals and i got what sisoft sandra is calling a clawhammer 3200+ but it only has 512k on the L2 cache.....im confused as all hell as to why its not listed as a newcastle when its only got 512k cache?!? any ideas?

 

[Markfw]

Check out this at newegg. Newcastle 2.2 ghz, 512k cache 3200+ for $218

 

[CyGoR]

Unforgiven, I just read about AMD making 3000+ Clawhammers out of 3200+ Clawhammers with cache problems. So they halve the cache size and sell it as a 3000+ while it's not a Newcastle.

Markfw900, I searched the AMD site, but the only 3200+ they produce is clocked ad 2.0GHz... Maybe it has something todo with the different socket types. The socket 939 CPU's only have 512Kb cache.
The 3400+ socket 754: 2.2GHz with 1MB cache
The 3400+ socket 939: 2.2GHZ with 512Kb cache.

But I can't find any 3200+ @ 2.2Ghz anywhere...

[edit]

No wait, now I'm VERY confused!!!!
I found This site from AMD, which says that there is a 3200+ running @ 2.2GHz and has 512Kb cache..
So they've ditched the 3200+ with 1MB?? Nice work AMD!

This is a Dutch Pricewatch which shows both 3200+ versions..
[/edit]

 

[Unforgiven]

yeah im looking at mine right here where it says in sisoft sandra and aida32 that its a clawhammer, in the newest version of cpu-z (1.23) it doenst post a name, in version 1.22 it shows up as a 2.2 ghz newcastle with 512k cache. holy smokes im lost! oh well, this beast hauls ass and its running seti like the wind. im just confused as all hell as to what all this means. its like a neutered clawhammer but with a higher operating speed instead of the extra 512k cache!

 

[CyGoR]

 

[CraigRT]

Originally posted by: CyGoR
The 3200+ is only available at a speed of 2000Mhz with 1MB cache. Unless you've got the mobile version of the CPU, don't know the specs of those..

I've got the 3000+ with 512Kb cache, the only difference with the 3200+.
When I run my CPU @ 2.2Ghz Seti times are also between 1h:50m and 2h:0m.
Default, @ 2Ghz, times are a little over 2hrs. Running WinXP with 1024Mb RAM on a Abit KV8-Max3 (Via).

NewCastle CPU = 512k
ClawHammer CPU = 1meg

NewCastle 3200+ = 2.2GHz and 512k cache
ClawHammer 3200+ = 2.0GHz and 1meg cache

my CPU is all at default settings, I can take screenshots if people don't believe me
cpu-Z 1.23 does not display my CPU correctly, either. (nothing showing at all) weird!

 

[Unforgiven]

im gonna give myself a few days of running 24/7, then post my results after i have a better cross-section of data to review.

 

[Unforgiven]

after 3 days of running i think its safe to say that on my 3200+(512k cache/@2.2 ghz) outputs a seti unit using the old 3.03 client in about 1:50-2:10 depending on angle range. times seems to be in between those 2

 

[Spacehead]

Originally posted by: Unforgiven
after 3 days of running i think its safe to say that on my 3200+(512k cache/@2.2 ghz) outputs a seti unit using the old 3.03 client in about 1:50-2:10 depending on angle range. times seems to be in between those 2

I could live with that. nice!

 

[CraigRT]

Originally posted by: Unforgiven
after 3 days of running i think its safe to say that on my 3200+(512k cache/@2.2 ghz) outputs a seti unit using the old 3.03 client in about 1:50-2:10 depending on angle range. times seems to be in between those 2

I found something strange.
my WU times were exactly like yours, right about a 2H average, but when I swapped out my 1GB PC3200 for my 512MB PC3500 for some OCing, and I tightened all the memory timings, my WU's are about 2:30 now.
seems unexplainable really, so I am going to swap in the PC3200 again and run at CAS3 again...

weird finding indeed.. this is on a Soltek K8AN2E-GR with a Newcastle 3200+ (stock)