Stories
Slash Boxes
Comments

News for nerds, stuff that matters

Slashdot Log In

Log In

Create Account  |  Retrieve Password

AMD's Dual-core Athlon 64 X2 reviewed

Posted by Hemos on Mon May 09, 2005 09:30 AM
from the lots-of-reviews dept.
ChocolateJesus writes "Weeks after formally announcing its dual-core Athlon X2 desktop processor, reviews are finally trickling out. The Tech Report's coverage tests two flavors of the Athlon 64 X2 against a whopping 17 competitors, including AMD and Intel's fastest single- and dual-core offerings. They've even thrown in a handful of dual-processor systems (and dual-core, dual-processor systems) for good measure. Testing focuses on multi-threaded applications, and the X2s deliver remarkable performance. Perhaps even more impressive is the fact that unlike Intel's dual-core Pentiums, AMD's X2s consume no more power than single-core chips." Looks like this story has come out of embargo - if you've find more reviews, post them in comments.
+ -
story
This discussion has been archived. No new comments can be posted.
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More
Loading... please wait.
  • Cooling (Score:4, Interesting)

    by Anonymous Coward on Monday May 09 2005, @09:33AM (#12477148)
    I don't get how this can run on the same power level as the single core chips. Can someone explain on how this is possible?
    • Re:Cooling (Score:5, Informative)

      by masklinn (823351) <slashdot...org@@@masklinn...net> on Monday May 09 2005, @09:41AM (#12477242)
      Specific design and use of a modified version of the most recent AMD core (Venice). Venice's consumption is much lower than it's parent (Winchester core), check the graphs, Dual Cores' power consumption is a bit higher than the 3800+ Venice processor.

      On top of that, A64 platforms are known for their low power consumption compared to Netburst based processors.
    • Re:Cooling (Score:5, Funny)

      by 0x461FAB0BD7D2 (812236) on Monday May 09 2005, @09:41AM (#12477250) Journal
      Easy. Multi-threaded electricity.
    • Re:Cooling (Score:5, Informative)

      by Kobun (668169) on Monday May 09 2005, @09:41AM (#12477254)
      Over at Anandtech, they have a similar article up.

      http://www.anandtech.com/cpuchipsets/showdoc.aspx? i=2410&p=2 [anandtech.com]

      On that page they compare a 130nm single core Athlon to a 90nm dual core. Even under a full load, the 90nm dual core uses less power than the single core 130nm chip.
      • Re:Cooling (Score:3, Informative)

        For a smaller manufacturing process (90nm), the transistors are smaller. On the single-transistor level, at least, they require less power to operate than 180 or 130nm transistors.

        Other considerations factor in to determine the power consumption (total number of transistors, other elements, arrangement, etc.), but the smaller size drops the power level quite a bit beforehand.
    • Sayeth Anandtech [anandtech.com]: ...the Athlon 64 X2 will consume less power than a 130nm Athlon 64, and less than 20% more power than a 90nm Athlon 64. Note that the Athlon 64 X2 4200+ compared here also consumes less power than all single core 90nm Intel Pentium 4 CPUs, even the Athlon 64 X2 4800+ consumes less power than all single core 90nm Pentium 4 CPUs.
    • Re:Cooling (Score:4, Insightful)

      by nokiator (781573) on Monday May 09 2005, @02:28PM (#12480210) Journal
      Comparing the X2s against 130nm Athlon 64 is not fair. As expected, the new X2 Athlons do burn more power than a single core Athlon 64 built on the same core/process at the same frequency. The amazing thing is that the difference appears to be only around 20%, which is almost unbelievable.

      You would expect to see less than 100% increase in the case of a dual core CPU due like the shared components which are not replicated:

      - The X2 chips still have a single, 128-bit wide memory controller. Since the memory controller charges/discharges external bit lines going to DIMMs, they do burn quite a bit of power. This power consumption is not duplicated in the case of a dual core CPU.

      - The X2 chips still have a single HyperTransport bus. The power consumption of this bus is the approximately the same between a dual core and single core CPU.

      However, power scaling due to these shared components would probably not explain how a dual core chip can burn only 20% more power. For both of the above cases, you could argue that one should expect to see higher utilization of the memory bus and the HyperTransport bus, so the exact power consumption contribution is not entirely clear.

      One thing to note that, AMD Athlon 64 cores tend to burn much less power in idle state compared to Intel chips. This is probably due to choices AMD made both in architecture and process. So the fundemantal reason why AMD X2 chips have such minimal incremental power consumption over single core chips is that one of the cores is typically underutilized most of the time and therefore burns much less power.

  • Anand's Take (Score:5, Informative)

    by Anonymous Coward on Monday May 09 2005, @09:34AM (#12477164)
    Here's Anandtech's review of the X2 [anandtech.com].
  • While the AMD 64 X2 Dualcore is impressive, I am still waiting for the AMD 69 XXX Hardcore myself.

    Sorry, it just had to be said.
  • by Anonymous Coward on Monday May 09 2005, @09:38AM (#12477213)

    No actually, they're going to be launched in June. The fact that this would be lost on the submitter was so obvious, I was able to prepare this message in advance and just paste it in.

    These look to be amazing CPUs. After the initial linpack-with-large-matrices benchmark, you have to go thirteen pages into the benchmarks at TechReport [techreport.com] to find some of note where the Intel solutions are able to score off a win!

  • Don't Forget the [H] (Score:5, Informative)

    by Unholy_Kingfish (614606) on Monday May 09 2005, @09:39AM (#12477223) Homepage
    The cold dark [H]OCP [hardocp.com] also has their preview [hardocp.com] up.

    Or you can jump right to their conclusions [hardocp.com].

  • Rollout process (Score:5, Interesting)

    by fbody98 (881072) on Monday May 09 2005, @09:39AM (#12477229)
    I'm relieve to see at least one thing out of this launch, and I would hope that other companies would do as much. AMD has clearly defined their rollout process so there will be no confusions and hopefully no false expectations.

    1. Announcement
    2. Technical Preview (benchmarks Appear)
    3. Launch (OEM Availability)
    4. Ramp-up and Reseller Availability

    They even give dates, if they can keep to those dates then we might actually have a product launch that doesn't antagonize the community with accusations of a 'paper launch'.

    I'd like to see more companies be more upfront about this.
  • vs (Score:3, Insightful)

    by Doc Ruby (173196) on Monday May 09 2005, @09:41AM (#12477251) Homepage Journal
    This is all getting very complex in the "Pentium compatible" world. Where's a chart of direct CPU performance comparisons across manufacturers (Intel, AMD, etc), so I can look up a potential purchase? Eg, I see that PriceWatch has an "Athlon XP 3000" at $102, and a P4/2.26GHz at $111. How much faster/slower will my LAME encoder server run for the $9 difference? At the very least, where's a chart showing which makes/models are direct competitors?
  • by amichalo (132545) on Monday May 09 2005, @09:51AM (#12477376)
    Does dual core have to mean 2 of the SAME processor?

    I recall reading a /. comment on a previous news day that suggested using dual core to allow the OS and anti-virus software run on one proc, while applications share another, thus improving stability/security/performance.

    But does a vendor HAVE to make a dual core chip with two of the same processor? Perhaps gains could be made using a less powerful, commodity chip core and pairing it to a top of the line core.

    Costs would be lower and they could sell more of this hybrid dual core because they would only need 1 top of the line cores.

    Oh, you get what I am saying.
    • But does a vendor HAVE to make a dual core chip with two of the same processor? Perhaps gains could be made using a less powerful, commodity chip core and pairing it to a top of the line core.

      But the less powerful core does not exist, so they'd have to design it. And the design cost is killer.

      However, assuming unlimited design budget and schedule, there are some academic papers showing that heterogeneous cores are a good idea.
    • by jericho4.0 (565125) on Monday May 09 2005, @11:23AM (#12478247)
      Yes, they have to be the same processor. The chipset design assumes that both processes are equally capable. Last time I built a dual processor machine, it was recommended that the CPUs have the same stepping number (same batch off the line).
      • Not only that, but scheduling algorithms for heterogeneous processors are a whole lot more complicated than those for homogenous sets (see the problems with getting good performance out of HyperThreading for an example). It might be possible to do something fairly simple, like run all processes on the slow processor and migrate them to the fast one when they use more than a certain percentage of the CPU speed, but in this case why not just down-clock the faster one when it is not in use?

        The only time when heterogeneous processors are really useful is when each is better than the others at a sub-set of tasks. Current PCs are usually a set of 3 different processors in a single box[1]. They have a reasonably fast general purpose CPU, and on the same die a simple vector processor (e.g. MMX, SSE, AltiVec), which has a different instruction set to the main processor and must be invoked explicitly. They also have a highly parallel large vector processor on a separate chip, which is usually used for graphics. No automatic scheduling is performed between these - it is up to the programmer to explicitly code for each one. Ideally, a heterogeneous processing environment would require code to be JIT compiled for each processor, and then moved between them depending on run-time profiling information.

        [1] Yes, this is an oversimplification.

  • by Senor_Programmer (876714) on Monday May 09 2005, @09:56AM (#12477435)
    "... AMD's X2s consume no more power than single-core chips."

    This is significant if you live in say Honolulu where electricity is 14cents/KWh or on Kauai where it's close to 22cents/KWh.
  • RISC (Score:3, Interesting)

    by delirium of disorder (701392) on Monday May 09 2005, @10:14AM (#12477583) Homepage Journal
    Packing all this circuitry will cost more in heat and fabrication costs then conventional cpus. SPARC and MIPS CPUs get more flops, mips, and overall thoroughput per watt and per millions of transistors on a die. Maybe we will see a resurgence of eligent RISC designs as dual/quad/oct core chips become more previlent.
  • by Dr. Damage (123558) on Monday May 09 2005, @10:38AM (#12477821)
    Sorry about our server's inability to keep up right now. We have a mirror here: http://www2.techreport.com/ [techreport.com]
    • by mattmentecky (799199) on Monday May 09 2005, @09:40AM (#12477238)
      That a lot of applications are not multithreaded. Thus wont get the speed advantage of the Duel-Core processor.

      Thats because the two cores are too busy fighting.
    • it does not have to be the same application. I have seen the environments where the business users are crippled because they have over-agressive anti-virus running in the background. Their apps would fly with a dual-core (or even hyperthreading).
      • A lot of the CPU burn with AV software involves doing I/O or scanning memory, neither of which are speeded by a dual-core processor. So you might get some speedup from this, but it won't be the difference between sluggish and speedy - it'll be sluggish versus less sluggish.
    • What a lot of people dont realize (Including a lot of programmers). That a lot of applications are not multithreaded. Thus wont get the speed advantage of the Duel-Core processor.

      Correct. Instead of executing the code in parallel, both cores will fight to the death for the privilege. Since only one core survives, you don't really get much benefit from duel-core processors.
    • by tinrobot (314936) on Monday May 09 2005, @09:45AM (#12477313)
      A dual CPU machine provides such a smooth operating environemnt. Never hiccups or pauses. I'm hooked on them. I hope dual core provides the same interactivity.
      • Hit the nail on the head.

        Certain image process apps (e.g.: enblend, a panorama enhancing app) drive my single athlon into a state where it is sluggish and hard to use (1.8ghz athlon, 768 mb ram, fedora core 3).

        So, while the Gimp can be compiled to do some multiply-threaded stuff, the real boost is that my computer should still be useable for other things while it's off fixing my panoramas.

        Since some of my panoramas take over 2 hours to fix, I'm looking into a faster system and will definitely be trying t
    • What a lot of people dont realize (Including a lot of programmers). That a lot of applications are not multithreaded. Thus wont get the speed advantage of the Duel-Core processor.
      And what YOU don't realize (including... duh... yourself?) is that running two or more applications at the same time will make use of dual core system, even if the apps themselves are single threaded (which is mostly true for games, quite a lot of desktop apps are at least a bit multithreaded).
      And a singlethreaded badly written application will be less prone to lock your computer, too, since the other apps will still be able to run from the second core.

      The main issue is not the multithreading abilities of the applications, but the multithreading abilities of the OS itself. If the OS handles multithreading well, multicore (physical or virtual) will always give a slight to impressive improvement over single core.
    • ps -eLFwww

      A lot more common apps are multithreaded than people think. Nautilus, Firefox, OpenOffice, Gnome Terminal, and, um Gnome Weather Applet are all mutithreaded.

      Even if no apps on your system are multithreaded, if you're like the 99% of users who run multiple processes simultaneously, you'll still get an advantage. Your updating app runs on one core while your desktop runs on another, for example.

      • by Xoro (201854) on Monday May 09 2005, @10:10AM (#12477550)

        Dual CPU systems tho are useless to the home users, it's for businesses and scientists with more computing need. Real enterprise applications are multithreated.

        Not so!

        I was one of the lucky people buy a cheap dual Celeron setup right after that hack was first discovered and I can tell you that multiprocessors on the desktop rock. My old system was a dual Celeron 400, and while it couldn't compete with a modern system in terms of benchmark speed, it had my current 1400 MHz Celeron system beat bloody when it comes to interactivity and responsiveness -- that elusive "feel".

        The price is steep now, but don't let arguments about application benchmarks dissuade you from trying out multicore when prices go down. The Anandtech review cited about has some really telling benchmarks about how well a dual system performs when loaded down with multiple tasks.

        Unlike the unnoticeable 200 or 400 MHz incremental bumps you usually see with processors, dual core really brings something of value to the desktop user. Try it and you'll see.

    • SERVERS!

      Nothing sexier than a 16slot Blade server running Dual-Core Opterons. Equivelent of 32 cpus in 5u of space.

      MMMmmm...mmm...mmm...mmm...SEXY!

    • The market for this is everyone who uses an agressive anti-virus program. The AV will run on one prcessor, what you are doing on the other.

      It's a sad case that as malware becomes more previlent, hardware vendors win. Really, you can be productive with (for example) Win2K on a 1GHz machine and 256MB, in an office. Now add the wait as every file is scanned on access for viruses (per corporate policy), and the machine somehow becomes "too slow."

      OH well. I guess it's time to put all productivity applications on a Server & run them remotely. Again;-(
    • by jtpalinmajere (627101) on Monday May 09 2005, @09:53AM (#12477407)
      For Intel, your argument definitely holds water. Their whole business plan has been based off of their vast number of production plants and relatively cheap process of putting hordes of chips on the market... hopefully making the chips pervasive enough to strike a profit level in the end (more like early mid-life with their price schemes though). It is only after a processor has been found tried and true that Intel migrates it to server land.

      AMD on the other hand has always started out chips on the enthusiast / enterprise market because they simply don't have the fabrication capacity that Intel does. Thus they market first for the high end users and over time the processors find their way into the desktop market when they've been dated by yet another new, improved processor being marketed at the first group. Their whole revenue plan is based off of the 'rich' people niche (which includes many medium to large businesses). Based on their success, I'd say that they've done really well with this business model and continuing to do so would likely continue to work for them.

      The common misnomer that is latched onto with many processor reviews nowadays is that both AMD and Intel are prodcing processors for the desktop platform, when in reality their business goals for their processors are on opposite spectrums. Intel starts desktop side, AMD starts server side. It is only after both have matured to some degree (and software caught up to both of them) that the processors can be meaningfully compared for the average joe user that just bought a new computer (or had one built for him).

      Most people who go crazy over these new technologies are either wanting it for pure bragging rights, or simply aren't aware of how little it will actually do for them... or both in all liklihood.
      • Re:market for this? (Score:5, Informative)

        by pjrc (134994) <paul@pjrc.com> on Monday May 09 2005, @11:43AM (#12478483) Homepage Journal
        AMD on the other hand has always started out chips on the enthusiast / enterprise

        s/always/recently/

        Clearly, you've just not been around very long, or not paying attention, or have only short-term memory.

        It's only been in recent years that AMD has bested Intel, performance-wise. For many, many years, AMD could release a new chip with good performance similar and then Intel would beat them with another new chip.

        There's a long, long history of AMD selling their chips at approximately half the price. Certainly through all of the 90's (486, pentium 1/2/3), AMD chips were substantially cheaper than buying Intel.

        During much of this time, AMD's chips also had a strong reputation to run very hot. Intel had a reputation for running cool and being easy to overclock. It was Intel that introduced the multiplier locks to prevent overclocking, which apparantly became quite a problem outside the USA where unscrupulous companies would sand down the tops of the chips (back then they were usually ceramic on top) and print a faster speed and resell them as such.

        It wasn't even all that long ago when the infamous celeron 300A, which was multiplier locked, could overclock to 450 MHz (then, nearly the fastest chip they sold) by overclocking the front side bus by 50%. At the time, AMD's chips were far behind, and they were running hot with very little overclocking margin, just to try closing the substantial perforance gap.

        Even back in the early Pentium days, even before AMD came out with a comperable chip, the 90 MHz pentium appeared in a new, smaller geometry process that made it run about as cool as the 486 66's.

        Intel has indeed been in the lead, technologically, for a very long time... ever since they stopped licensing IP from Intel. For a bit of really ancient history, long ago, some large well known companies had a strong policy of never using any components that were not available from a second source. AMD's business model 20+ years ago was to license designs and be that second source.

        Even a number of articles mention how the tables have turned recently, and speculate whether Intel will regain the honor of top performance.

        I'm not affiliated with Intel, and in fact the PC I'm using to write this comment runs an AMD chip. When I upgrade, it'll probably be AMD again. Recently, AMD appears to have made some really smart architectual decisions that have put them in the lead, technology-wise.

        But to believe such has always been the case, or even been a trend that's anything more than recent, is to ignore or be utterly ignorant of the very long history of Intel dominating the PC / x86 market with the best chips.

    • If they ever make it to a significant size of the market, you will see more of the CPU intensive tasks that people do today becoming multi-threaded. Some of the of long running processes that are common on home computers lend themselves nicely to divide and conquer, such as ripping music or video. By going dual core or SMP, one can halve the processing time without having to wait a few years for the processing power of CPUs to double.
    • by segmond (34052) on Monday May 09 2005, @09:57AM (#12477441)
      You are right that the market for dual core processors for home users is really not there, but it could be. Think of the BeBox/BeOS, It was a system that was designed for dual core processors and all applications compiled for BeOS automatically benefited from it. What is missing in the x86 world for home users is such an OS. I believe that Intel/AMD are well aware of this, and this belief leads me to the conclusion that they are not really pumping out such systems for the average home users, it is more for businesses. Internet/Enterprise servers will definitely benefit more from it.
    • Longhorn (Score:5, Funny)

      by yabos (719499) on Monday May 09 2005, @09:57AM (#12477447)
      Have you seen the specs required for Longhorn!
    • Re:market for this? (Score:4, Interesting)

      by be-fan (61476) on Monday May 09 2005, @10:02AM (#12477490)
      Programmers? Multimedia people? Scientific computing folks? There are quite a few markets that can use dual-core right now. Basically, anybody who buys a PowerMac :) Moreover, in the future, everyone will have to move to dual core (including gamers), because AMD and Intel cannot ramp up the clockspeed of single core chips. So AMD's strategy makes quite a bit of sense. Sell dual-core chips to the high-end now (notice how all of these CPUs are high-end chips that carry quite a price premium), and start getting the ball rolling on multithreaded software.
    • Gamers need dual core processors. Many games are still single threaded but that's probably the past. There is plenty to be gained from a single game running multiple threads. The only concern is that RIGHT NOW I don't think Windows will do The Right Things. I could be wrong.

      The question is, other than gamers and graphic artists, who needs them? You have a point in that almost every other application that the average guy uses has been saturated in terms of (quite prolific) features for years. I really don't

    • who is going to buy computers with these new ultra powerful dual core processors?

      I will. I'm often running applications that take 100% CPU. Having another core around to make the system nice and responsive would be wonderful.

      gamers don't need dual core

      Right, and when video cards that supported an accelerated transform and lighting (i.e. the GeForce) came out, they didn't need that either since current games didn't support it. You can bet the next core of games will be multi-threaded.

      everyday use
    • Re:market for this? (Score:5, Interesting)

      by quarkscat (697644) on Monday May 09 2005, @10:35AM (#12477798)
      Scientific workstations?

      Anyone involved in matrix math (circuit design, mechanical engineering, fluid dynamics, etcetera) would love to be able to do this on their desktop instead of shared time on an HPC. Or combine the computational power of an office full of these machines at night or over weekends for the really big jobs. What's not to like?

      Any scientific organization that has been holding off on capital expeditures while waiting for a clear winner to emerge ((AMD vs. Intel) vs. (PPC vs. SPARC)) will have come that much closer to making a decision.

      Intel's IA64 gambit has not panned out -- their marketing hype has brought down some of their competition (PA-RISC and MIPS), but it has not proven to be the market leader Intel would have hoped. But like a wildfire in the woods, Intel's IA64 has opened up competition for diversity and some new leadership.
    • by johnw (3725) on Monday May 09 2005, @11:49AM (#12478561)
      My mind is boggled by questions like this. Are there really people out there who still use their computers for just one thing at a time?

      The machine I'm typing this on (just a simple diskless workstation) currently has 75 different processes running. The server it's connected to has 145. With a dual core processor in either of them, the number of processes able to run simultaneously would be increased by 100%.

      The idea of running just one application on your box went out more than 10 years ago. Wake up and smell the coffee.

      (If nothing else, all those blasted Flash animations can run without chewing up CPU cycles I would rather use for something else.)

      John
      • by prisoner-of-enigma (535770) on Monday May 09 2005, @01:11PM (#12479473) Homepage
        Microsoft's official licensing stance remains that one die = one CPU.

        No, Microsoft's official licensing policy is one socket = one CPU. Therefore, a dual-socket Opteron motherboard with two dual-core chips would be licensed as a dual-CPU system, even though it has four separate cores.

        I think your post was trying to get that idea across, but your statement of "one die = one CPU" is misleading to that effect.

        What's odd about this is if you bought a dual-core, dual-CPU Xeon system supporting HyperThreading. If you opened up Task Manager you'd find eight CPU graphs. Not that you'd get anything near the performance of a eight-way system, though...

        Microsoft's licensing is a bright spot when it comes to commercial software and multi-core CPU's. There are several firms still clinging to the "one core = one CPU" model, and dual core chips are going to immediately make such software very expensive.

        I contacted Oracle a couple of weeks ago to clarify their position, and I was told then that dual-core chips would be considered a single CPU for the purposes of licensing. It seems that Microsoft's adherence to the "one socket = one core" idea is forcing its competitors into the same pricing model. Who woulda thunk Microsoft would actually be helpful in this situation?