Page 1 of 1

how do you know where your processor came from?

PostPosted: Mon Jan 23, 2006 12:05 pm
by legoalex2000
i've heard multiple times about the AMD san diego processor. now as far as i remember, AMD only has 1 plant (i could be wrong).

so if there is more than one plant, how do i know where my CPU came from?

:)Ramos

Re: how do you know where your processor came from

PostPosted: Mon Jan 23, 2006 12:37 pm
by Delta_
I'm not sure, but i believe they name the processors after places so that they can be told apart, like a codename. ;)

Re: how do you know where your processor came from

PostPosted: Mon Jan 23, 2006 12:40 pm
by KDSM
correct they are codenames

Re: how do you know where your processor came from

PostPosted: Mon Jan 23, 2006 5:40 pm
by ctjoyce
Not really, Core names ;) Like prescott or Clawhammer. Its just a fast way of telling what famly your processer came from and some quick specs on it without going into specifics.

Cheers
Cameron

Re: how do you know where your processor came from

PostPosted: Mon Jan 23, 2006 6:43 pm
by legoalex2000
so how do i figure out mine?

:)Ramos

Re: how do you know where your processor came from

PostPosted: Mon Jan 23, 2006 6:51 pm
by Jared
so how do i figure out mine?

:)Ramos


psst...

www.google.com


sorry I'm in one of my moods and I have no clue about what you are talking about.. ;)

Re: how do you know where your processor came from

PostPosted: Mon Jan 23, 2006 9:22 pm
by ctjoyce
so how do i figure out mine?

:)Ramos



It came from an AMD plant ;) You may be able to look at the chip itself and find out, but there isnt a better answer than that.

Cheers
Cameron

Re: how do you know where your processor came from

PostPosted: Mon Jan 23, 2006 9:30 pm
by legoalex2000


It came from an AMD plant ;) You may be able to look at the chip itself and find out, but there isnt a better answer than that.

Cheers
Cameron


yeah hang on, just lemme pull out my CPU... wait for it... ahh....

























riiight, like i'd just pull out the CPU, im starter now, just ask e to do that 4 years ago and i probably would've done it :P

as far as i know it's a san diego core, ause appearantly there is a Venice core....

:)Ramos

Re: how do you know where your processor came from

PostPosted: Tue Jan 24, 2006 3:18 am
by Delta_
San Diego cores have double L2 cache of Venice cores.  So are faster. ;)

Re: how do you know where your processor came from

PostPosted: Tue Jan 24, 2006 6:04 am
by chuckcrc
Check out this link at AMD. It will tell you how to de code the numbers on your chip.
cheers
chuck
http://www.amd.com/gb-uk/assets/content_type/DownloadableAssets/Processor_Recognition_Rev05_ENG.pdf

Re: how do you know where your processor came from

PostPosted: Tue Jan 24, 2006 7:06 am
by Weather_Man
CPU-Z will give you that info. Easy to use.

http://www.cpuid.org/cpuz.php

Re: how do you know where your processor came from

PostPosted: Tue Jan 24, 2006 10:24 am
by congo
ASSEMBLED IN MALAYSIA

Re: how do you know where your processor came from

PostPosted: Tue Jan 24, 2006 1:26 pm
by legoalex2000
found out my core is a venice core, not a san diego core.

:)Ramos

Re: how do you know where your processor came from

PostPosted: Wed Jan 25, 2006 1:19 am
by congo
The only people with San Diego cores are probably already aware of it. Firstly, no company is going to fit San Diego's as standard when they cost more, so that only leaves the private system builder who knows exactly what he wants and is willing to pay the extra for it.

At first glance, a 3500+ looks like a real bargain next to a 3700+, the Speed is identical but the 3500+ is much cheaper. Pity this isn't the reality as this is one case in which you get what you pay for.

;)

Re: how do you know where your processor came from

PostPosted: Wed Jan 25, 2006 6:35 am
by ctjoyce
Yes I do feel bad for those who look only at core clock, and not L2 chache or process thread etc. However it is rather funny when they try to figure out why you have the same core clock, and a better computer then they do with exactly the same specs but the processer.

Cheers
Cameron