Final Words

At this point, having seen dual core CPUs from both AMD and Intel, there's no question that dual core is desirable on all fronts; whether we're talking about the server world or on your desktop, dual core improves performance by a noticeable amount and the performance benefits will only get better down the road.

As a server solution, the dual core Opterons enable a whole new class of performance to be realized on platforms. Two socket servers will now be capable of having the performance of a 4-way system, something that has never been possible in the past. AMD's push with dual core into the server markets half a year before Intel's dual core Xeon arrives is going to tempt a lot of IT departments out there; the ability to get 4-way server performance at much lower prices is an advantage that can't be beat.

Despite AMD's lead in getting dual core server/workstation CPUs out to market, Intel has very little reason to worry from a market penetration standpoint. We've seen that even with a multi-year performance advantage, it is very tough for AMD to steal any significant business away from Intel, and we expect that the same will continue to be the case with the dual core Opteron. It's unfortunate for AMD that all of their hard work will amount to very little compared to what Intel is able to ship, but that has always been reality when it comes to the AMD/Intel competition.

On the desktop side, we are extremely excited about the Athlon 64 X2. The 4400+ that we compared here today had no problem competing with and outperforming Intel's fastest dual core CPUs in most cases, and at a price of $581, the 4400+ is the more reasonably priced of the X2 CPUs. That being said, we are concerned that availability of the lower cost X2 CPUs will be significantly more limited than the higher priced models. At the ~550 marker, your best bet is clear - the Athlon 64 X2 will be faster than anything that Intel has for the desktop.

What's quite impressive is how competitive the Athlon 64 X2 is across the board. With the Pentium D, we had to give up a noticeable amount of single threaded performance (compared to Intel's top of the line Pentium 4 CPUs) in order to get better multithreaded/multitasking performance, but with AMD, you don't have to make that sacrifice. Everything from gaming to compiling performance on the Athlon 64 X2 4400+ was extremely solid. In multithreaded/multitasking environments, the Athlon 64 X2 is even more impressive; video encoding is no longer an issue on AMD platforms. You no longer have to make a performance decision between great overall performance or great media encoding performance - AMD delivers both with the Athlon 64 X2. Also keep in mind that the performance preview that we gave of the Athlon 64 X2 today is actually a very conservative estimate. The shipping Athlon 64 X2 CPUs will run with regular DDR memory and with much faster motherboards - meaning that you should be prepared to be impressed even further down the road.

The real problem is that AMD has nothing cheaper than $530 that is available in dual core, and this is where Intel wins out. With dual core Pentium D CPUs starting at $241, Intel will be able to bring extremely solid multitasking performance to much lower price points than AMD will. And from what we've seen, it looks like that price advantage will continue for quite some time. It all boils down to economics, and in the sense of manufacturing capacity, Intel has AMD beat - thus allowing for much more aggressively priced volume dual core solutions. Then there's the issue of availability; as impressive as AMD's dual core desktop offerings are, we're honestly worried that we won't see any real volume until late this year at best. Intel does have a golden opportunity now to really step forward and regain some enthusiast marketshare, but we seriously doubt that we'll see anything faster than the Pentium D 3.2 anytime soon. It's strange how tables have turned, making Intel look like the value CPU manufacturer in the dual core race.

Now that we've seen both AMD and Intel dual core solutions, it's time to play the waiting game. Dual core Opteron 8xx series CPUs should be available now, with the 2xx and 1xx series following in about a month. The Pentium D and Pentium Extreme Edition should be shipping before the end of this month, with expected retail availability next month. And the big wait, of course, will be for the Athlon 64 X2, which will be available towards the end of this year.

Our dual core coverage does not stop here. We have more in the works including the promised Workstation comparison, a look at how multitasking in Linux is impacted by dual core, and even more multitasking scenarios modeled based on your feedback (so, keep it coming).

Gaming Multitasking Scenario
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