Earlier this month, Intel introduced their first dual core desktop CPUs - the Pentium D and the Pentium Extreme Edition.  Coupled with extremely aggressive pricing designed to move the majority of the desktop market to dual core within the next two years, Intel's launch did not cease to impress.  The ability to bring workstation class performance in multithreaded and multitasking environments to the desktop, at an affordable price, is something that we've been hoping for for years.  Intel's launch was pretty interesting, but today, AMD has more bang.

From the beginning, AMD has talked about how they were going to bring dual core to the K8 architecture.  The on-die north bridge, a part of every Athlon 64 and Opteron CPU, was designed from the ground up to be able to support multiple cores.  AMD had designed their first dual core K8 CPUs years ago. They were simply waiting for manufacturing processes to mature in order to actually make producing such a chip a feasible endeavor. 

With their 90nm process finally maturing, it made business and financial sense to introduce their first dual core products.  AMD wasn't alone in their decision, as it's obvious that Intel waited for 90nm before making their move to dual core as well.  The problem for both AMD and Intel is that at 90nm, a dual core chip is getting a bit on the large side.  Intel's first dual core CPUs weigh in at 230 million transistors on a 206 mm2 die, and AMD's new CPUs are a bit obese themselves at 233.2 million transistors on a 199 mm2 die.  While the dual core CPUs that we have tested from both AMD and Intel are no slouch, it's clear that both companies are working to transition to 65nm as quickly as possible to make manufacturing these chips much more reasonable.

Although this may seem like a tangent to the topic at hand, manufacturing has a lot to do with today's announcements from AMD.  What exactly is being announced?  Well, for starters, AMD is announcing their first dual core Opteron parts.  The word "announcing" in this sense means that they are declaring availability of their 800 series dual core Opteron CPUs, and promising that 200 and 100 series dual core Opteron CPUs will be made available starting next month.  Before we move on to the rest of the announcement, pay very close attention to the parts for which AMD is announcing availability - the 800 series parts.  The Opteron 800 series CPUs are for use in 4 or more socket servers and are AMD's most expensive CPUs, and thus, their lowest volume CPUs.  Remember that at 90nm, AMD can produce around half as many dual core CPUs as they can single core CPUs per wafer - so they need to be very careful about demand.  You will notice later on in this article that AMD's strategy involves keeping prices higher and introducing lower quantity CPUs first, in order to ensure that their single core CPUs still have a market and that they aren't committing to more than what they can deliver.  At the end of the day, AMD is still a much smaller manufacturer than Intel and thus, they have to play their cards very differently, which leads us to the second part of AMD's announcement today: the new dual core desktop Athlon 64 X2 line.

The Athlon 64 X2 will be AMD's new brand for dual core desktop CPUs.  This line is being talked about today, but an official announcement with full benchmarks won't come until June.  That being said, we have made it a point to bring you a preview of Athlon 64 X2 performance in this article, despite the fact that AMD isn't introducing the chips for another two months.  So, for all of you who are interested to see how AMD's dual core desktop CPUs stack up against the recently introduced Pentium D, never fear, we have what you're looking for. 

The introduction of the Athlon 64 X2 brand also comes with a few other tidbits of information:
  1. The Athlon 64 4000+ was the last single core member of the Athlon 64 line.
  2. The Athlon 64 FX will continue as a single core CPU line, with the FX-57 (2.8GHz) due out later this year.
This article will serve two purposes. First and foremost, we're interested in the new dual core Opterons as a server solution - and we run them through our usual web and database serving tests.  Next, we're going to take a look at the Athlon 64 X2 and how it compares in performance to Intel's recently announced Pentium D.  We've developed even more desktop multitasking tests for this article, so we'll be able to provide you with an idea of how well AMD will be able to compete in the multi-core world. 

We are missing a look at workstation performance between the Opteron and Xeon, but rest assured that such a comparison is in the works.  The usual mix of very limited time and hardware problems (which we will also discuss in this article) forced us to exclude one of the comparisons, and thus, the workstation comparison will have to wait for another day. 

A Look at AMD’s Dual Core Architecture
Comments Locked

144 Comments

View All Comments

  • MDme - Friday, April 22, 2005 - link

    #92

    the difference between an opteron and an a64/fx is as follows:

    opteron - needs ECC memory cache is 1mb it is multiplier locked, COHERENT HT LINKS

    a64 - uses non-registered (non-ecc) memory (which is faster), cache 512k-1mb, multiplier locked

    a64fx - non-ecc memory, 1mb cache, unlocked.

    so opteron's are not a64/fx's but are quite similar. the main difference is the memory type and the COHERENT HT links

    therefore the X2 4400+ is really an opteron (dual core) running at 2.2 with dual 1mb cache but with the COHERENT HT link disabled that uses non-ECC ram.

    performance should therefore be almost identical between one DC opteron 2.2ghz and one A64 X2 4400+ (possibly the X2 will be faster 5%) due to the non-ECC memory which is faster.


  • tygrus - Friday, April 22, 2005 - link

    If you use a Opteron 875 then label it as such in all diagrams. You can make a note that the Athlon64 X2 4400+ will perform similarly to the Opteron 875. The differences in MB and RAM will affect results and so a direct re-labelling should not be made.
    Good database, multimedia, data analysis should make good use of multi-core/multi-CPU systems. When I mention data analysis I'm talking about software like SAS 9.1.3 and SAP. Even SAS is only threaded for a few tasks and is a big hassel to pipeline one step into another.
  • Some1ne - Thursday, April 21, 2005 - link

    Good article overall, although I question the validity of declaring that an Opteron 875 is roughly equivalent to an Athlon 64 4400+. I could be wrong, but surely there must be significant architectural differences between the server-class chip (top of the line server-class chip no less) and the desktop Athlon 64? If not then why the price premium for Opterons, and why don't manufacturers just find a way to kludge the Athlon64 to work in MP configurations as in theory if they are really equivalent when run at the same clock speed, it would be much more cost effective to use kludged Athlon 64's, and it would also let higher performance levels to be reached as the dual-core Athlon64's are slated to run at one clock increment higher than the fastest dual-core Opteron's? So anyways, is it *really* valid to treat an Opteron as being essentially equivalent to a similarly clocked Athlon64? As much as I love finally seeing Intel chips trounced pretty much across the board, it seems to me like the results could potentially be inaccurate given that an Opteron 875 was used and simply "labeled" as an Athlon64 4400+.
  • Cygni - Thursday, April 21, 2005 - link

    #89... seeing as how the Opty x75 and A64 X2 are based on functionally identical cores, thats not too likely at all. What DOES seem likely to me reading this article is that BIOS updates, and X2 support on 939 boards, is going to be a very interesting story to follow. It doesnt look like its too easy to get a solid AMD Dual Core BIOS if even Tyan is struggling, of all board mfts. May give a fiesty smaller board mft a chance to slam the bigboys and grab marketshare (such as ECS with the K7S5A).
  • Jason Clark - Thursday, April 21, 2005 - link

    saratoga, waah? There are similarities between C# and C++. While agree it's java'ish as well, it definitely has similarties to c++. One could say c# shaes similarities with c/c/c++.

    read away:

    http://www.mastercsharp.com/article.aspx?ArticleID...

    http://www.csharphelp.com/archives/archive138.html

    "C# is directly related to C and C++. This is not just an idea, this is real. As you recall C is a root for C++ and C++ is a superset of C. C and C++ shares several syntax, library and functionality." Quoted from above.

    L8r.




  • Jep4444 - Thursday, April 21, 2005 - link

    I've spoken to a few people from XS who have Engineering Samples of the Athlon X2s and all im hearing is that arent nearly as good as the dual core Opterons, they were apparently rushed
  • xtknight - Thursday, April 21, 2005 - link

    #86 - the r_smp cvar was disabled in quake3 in a patch, for a reason i don't know. i confirmed this by having quake3 crash on my p4 HT CPU with that setting enabled. as for doom3, i'm not sure. i'm guessing it's not implemented well enough yet...
  • Chuckles - Thursday, April 21, 2005 - link

    #83:
    "Real gamers" may use a single core, but I have been hankering for duallies since I tried an older dual G4 to my newer single G4. Even on the crappy MaxBus, I could browse the web, chat, do "real work" and game, without having everything go to pot when a bolus of e-mail came in.
    When you buy a dualie of any type, you buy the ability to do other stuff while you computer working on its latest task. Remember that when you get lagged while Outlook downloads your latest spam.

  • Googer - Thursday, April 21, 2005 - link

    Why wern't there any SMP Tests done on Quake 3 engine, after all it is said to be multithreaded.

    Also, Carmack said during the devlopment of DOOM3 that the engine was going to support multiple processors, did this ever happen? Does anyone know what the command might be for D3 console to enable SMP, like it's cousin? How much truth is there to this?
  • Nighteye2 - Thursday, April 21, 2005 - link

    Add to all the arguments that we can potentially see programs taking advantage of this quite soon...without the effort required to implement full multi-threading, game functions could be assigned to use the other processor if it's available. For example, AI can be done by one core, while the other core does the rest of running the game.

Log in

Don't have an account? Sign up now