Slashdot Mirror


65nm Athlons Debut With Lower Power Consumption

TheRaindog writes "AMD has finally rolled out Athlon 64 X2 processors based on 65nm process technology, and The Tech Report has an interesting look at their energy usage and overclocking potential compared to current 90nm models. The new 65nm chips consume less power at idle and under load than their 90nm counterparts, and appear to have plenty of headroom for overclocking. An Athlon 64 X2 5000+ that normally runs at 2.4 GHz was taken all the way up to 2.9 GHz with standard air cooling and only a marginal voltage boost, suggesting that we may see faster chips from AMD soon."

32 of 151 comments (clear)

  1. HTPC by tedgyz · · Score: 4, Interesting

    The little gem in this story is the Athlon 64 X2 3800+ EE SFF 2.0GHz. At 35W, that sounds like a perfect CPU choice for a super-silent HTPC.

    --
    "No matter where you go, there you are." -- Buckaroo Banzai
    1. Re:HTPC by Mayhem178 · · Score: 2, Informative

      What, your HTPC can't render Final Fantasy: The Spirits Within on the fly? Lame. ;)

      Okay, no, seriously. I have an Athlon X2 3800, and it runs deathly quiet for any operation I've thrown at it. Considering that the machine I have it in is my primary gaming PC, I'd say that's noteworthy. And I've never noticed any great amount of heat production, either.

      --

      "You will pay for your lack of vision..." - Emperor Palpatine to Ray Charles

    2. Re:HTPC by Neon+Spiral+Injector · · Score: 4, Insightful

      How do you suggest that one decode 1080i H.264 transport streams with AC3 5.1 audio? This processor may be slightly more than required, but not by much.

    3. Re:HTPC by javilon · · Score: 2, Interesting

      Do you know of any video player that will be capable of taking advantage of two processors?

      As far as I know mplayer doesn't, xine doesn't and vlc doesn't.

      --


      When his defense asked, "Which computer has Jon Johansen trespassed upon?" the answer was: "His own."
    4. Re:HTPC by Ultra64 · · Score: 5, Funny

      right, because it's totally impossible for a computer to run more than one program at a time.
      it's too bad video playing couldn't happen on one cpu while video compression happened on another.
      someone should invent that. it could be called "Sametime Many Programs" or "SMP" for short.

    5. Re:HTPC by Neon+Spiral+Injector · · Score: 4, Interesting

      OK, I'll give you that. But the HD H.264 requires a huge ammount of CPU to decode. My current dual 1.6 GHz Opteron system can't do it in real time. Doesn't even come close.

      So I was thinking the same thing about this new chip. It sounds pretty close to what I was wanting.

    6. Re:HTPC by Neon+Spiral+Injector · · Score: 2, Informative

      It is just this specific codec, any ffmpeg based player in either Linux or Windows just dies on 1080i H.264. 720p H.264 is fine, as is 1080i MPEG2. I also have some 1080p WMVs that play fine.

    7. Re:HTPC by Neon+Spiral+Injector · · Score: 2, Interesting

      Quicktime only seems to use a subset of the features of H.264. I can easily create videos that play fine with ffmpeg, but are a corrupted mess with the Quicktime player.

  2. It's a question of cores by BadAnalogyGuy · · Score: 5, Funny

    If you have only one core, you need to rely on the OS to not get in the way of running processes during task switches. With more than one core, processes can be split amongst the cores so that they do not need to be interrupted all the time by the OS timer interrupt handler. The more cores you have, the better you can scale up, even if the cores themselves are slower than a competing single core chip.

    It's like driving down the highway in your train vs riding the rails in your Audi. Sure, you can try to drive the car on the train tracks for a while, but eventually the springs will break and your tires will pop and you end up walking to your final destination. But if you took the train, you'd probably tear up the road and it would take a while since you couldn't get much traction with the large metal wheels, but since you're carrying a whole lot of stuff in the train cars being pulled behind you, your bandwidth / time ratio is very favorable.

    1. Re:It's a question of cores by KingArthur10 · · Score: 3, Interesting

      Concerning your analogy: I was thinking more along the lines that a train runs on a single track and sometimes has to be held up for another train to use the same track. They have some track switching, but most operations are serial. A car on the highway might not be allowed to go as fast as a train, but it's got four lanes to maneuver through. A bunch of cars will reach their destinations faster than a bunch of trains because the trains have to share single tracks often.

      --
      I came, I saw, She conquered.
    2. Re:It's a question of cores by pclminion · · Score: 2, Interesting

      Concerning the more serious first part of your post, it seems that ideally what you want to do is dedicate one CPU/core to interactive tasks, and another core for batch tasks. That way, the interactive tasks can easily interrupt each other as often as necessary on one CPU, while the other CPU cranks along on the batch tasks with a much longer time quantum without any unnecessary interruptions.

  3. Interesting.. by joshetc · · Score: 4, Funny

    considering my 3800+ X2 runs at 2.8ghz with 1.5V. 2.9ghz really doesnt seem like much for a higher end model.. I'm thinking they will need at least 3.1ghz or so overclocks on air to have much of a chance in most highend enthusiast rigs.

    1. Re:Interesting.. by gone9teen · · Score: 3, Informative

      You do realize, well obviously you don't, the clock speed of a processor means nothing between different models when it comes to performance. A newer 2.0 Core 2 Due processor SMOKES my 3.0 Pentium 4.

    2. Re:Interesting.. by joshetc · · Score: 5, Informative

      Duh, all athlon 64 dual cores to date are clock for clock nearly identical though. This means clock speed does matter. I can't believe you got modded up for making such a shitty assumption on a "geek" website.

    3. Re:Interesting.. by teg · · Score: 2, Informative

      Duh, all athlon 64 dual cores to date are clock for clock nearly identical though. This means clock speed does matter.

      They're almost identical - cache sizes vary, and, more importantly, the new ones (65 nm) have higher cache latency

      .
  4. As someone once said... by Anonymous Coward · · Score: 5, Funny

    A bad analogy is like a leaky screwdriver.

  5. Nice but a little slower. Surprise! by IPFreely · · Score: 3, Interesting

    Anand has a nice review of these new processors, including performance comparisons.

    The surprise is that it was a little slower than it's 90nm counterpart. They chased it down to the cache latency going up from 90nm to the 65nm part.

    Other than that, it looks good.

    --
    There is nothing so silly as other peoples traditions, and nothing so sacred as our own.
    1. Re:Nice but a little slower. Surprise! by MrFlibbs · · Score: 4, Informative

      According to the AnandTech article you referenced, saying that "it looks good" is a bit of an overstatement. Here are a few quotes from the article:

                "It's clear that these first 65nm chips, while lower power than their 90nm
                counterparts, aren't very good even by AMD's standards."

                "Performance and efficiency are still both Intel's fortes thanks to its Core 2
                lineup, and honestly the only reason to consider Brisbane is if you currently
                have a Socket-AM2 motherboard."

      In every single AnandTech benchmark, Intel wins in both raw performance and performance per watt. And if raw power consumption is important to you, the winner was a 90nm AMD SFF part. In no case was a 65nm AMD better at anything.

      The article does point out that a mature 90nm process is being compared to an immature 65nm process and thus future steppings are bound to be better. However, this doesn't change the fact that the current crop of AMD 65nm parts are a major disappointment.

  6. Lower heat (and performance, ....) by IYagami · · Score: 2, Informative

    ...But most of the time irrelevant.

    Anandtech has two good reviews here (lower power) and here (lower performance)

    The main reason is the increase of L2 Cache Latency from 12 cycles to 20. But in most of the benchmarks the difference is very low.

  7. Good news, guys! by Black+Parrot · · Score: 4, Funny

    Next time your class stud mentions his 9", you can counter by mentioning that your 6.5" consumes less power and gets the job done faster!

    --
    Sheesh, evil *and* a jerk. -- Jade
  8. Re:I wouldn't overclock an AMD by vslashg · · Score: 2, Funny
    I've had bad experiences overclocking AMD processors (considering extended usage >6 months and at 100% load) with proper refrigeration. Unfortunately those processors tend do break (with no prior warning) eventually. What's a pity, since they overclock well.
    They tend to break when overclocked, and yet they overclock "well"?

    I don't think that word means what you think it means.
  9. Re:SMP by Anonymous Coward · · Score: 5, Funny

    Whooosh....!

  10. Take my advice....please by OneSmartFellow · · Score: 3, Interesting

    If you are about to buy a AMD chip, ensure you buy a AM2 version, this is becuase non-AM2 versions do no support low level Hardware Virtualization (which means that XEN - and competitiors - can only operate in a paravirtualization mode)

    1. Re:Take my advice....please by Courageous · · Score: 2, Informative

      This is if you want to run Windows guests. Linux guests are best run paravirtualized for performance reasons. But point well-taken.

      C//

    2. Re:Take my advice....please by TheRaven64 · · Score: 2, Interesting
      True, but only as far as it goes. On x86, you have four protection rings. The hypervisor lives in ring 0, the kernel gets moved to ring 1, and the apps go in ring 3 as usual. When they designed x86-64, AMD 'helpfully' removed rings 1 and 2, so now the kernel and the apps have to share the same ring. They also removed the segmented memory model, so you have to use (more expensive) paged protection mechanisms to protect guests from each other. This makes paravirtualisation more expensive on 64-bit x86 systems than 32-bit ones. If you have a system that supports HVM, you can put the Hypervisor in the special hypervisor mode, use hardware-assistance for shadow page tables, and generally implement paravirtualisation more efficiently.

      I can't remember if current releases of Xen do this, but if they don't then they definitely will in the next six months.

      --
      I am TheRaven on Soylent News
  11. 65nm version marginally slower than 90nm version by MajorJuggler · · Score: 2, Interesting

    Apparently Brisbane (65nm) has a 20-cycle L2 cache latency, vs. the 12-cycle latency from the 90nm versions. http://www.anandtech.com/cpuchipsets/showdoc.aspx? i=2893&p=3

  12. Re:Love the testing by GodsMadClown · · Score: 2, Insightful

    They used the same video card on the Intel test rig too. They're just trying to keep as many components as possible in common between the platforms so that the power draw comparisons are more useful.

    Not too complicated really. As to why they chose that particular video card, I don't know, but I'd wager that the reviewer just had it on hand.

  13. OT by Spaceman40 · · Score: 3, Funny

    We really need a "Whoosh" mod.

    --
    I [may] disapprove of what you say, but I will defend to the death your right to say it.
  14. Re:I wouldn't overclock an AMD by dtjohnson · · Score: 2, Insightful

    I overclocked the very first stepping of the first 500 Mhz Athlon to 700 Mhz and it has been running 24/7 for 6 years. Now, it is finally being replaced with a newer (AMD of course) system and I opened up the case for salvage parts and there...there was the overclocking board still attached to the 'Slot A' CPU and still working perfectly. I'd forgotten it was even there. So there's a 6-year data point on the overclocking/longevity scale.

  15. Re:Sempron by Endo13 · · Score: 2, Interesting

    Obvious troll, but I'll bite. The 32-bit Sempron is nothing more or less than the continuation of the old 32-bit Athlon XP CPU line, and Semprons carrying the same numerical designation as their old Athlon XP counterparts have exactly the same specs. Why they changed the name I'm not exactly sure, but it's still the exact same CPU. Celerons on the other hand are just Pentiums without most of the L2 cache, which makes them heavily crippled since the P4 with its long pipeline depends very much on their on-die cache.

    --
    There is no -1 Disagree mod. Slashdot.org/faq defines mod options. USE IT.
  16. A major disappointment for whom? by John+Jamieson · · Score: 4, Interesting

    Whenever AMD or Intel moves to a new process, they do not expect much from the first cores(they are happy if they get as many cores from a wafer as they did before-which if my sources are correct, Intel didn't do, and AMD has).
    A lot of people forget that when Intel moved to 65nm, the new chips were slower in many ways, and the clock speeds were lower than the top end 90nm P4's.
    By industry standards these AMD 65nm chips are a SUCCESS.

    My only beef with the 65nm Athlons is that I cannot buy one at newegg, or order one from DELL. In my world, if I cannot order a PC with one, or buy it at newegg, IT IS A PAPER LAUNCH!

  17. A follow-up on L2 cache performance by Dr.+Damage · · Score: 2, Interesting

    I have posted an update to my initial look at AMD's 65nm processors here:

    http://techreport.com/onearticle.x/11486

    The update addresses some anomalies in L2 cache performance and raises some possibly related questions about die sizes for the 65nm Athlon 64 X2. It appears this chip is not just a die shrink with the same performance characteristics, after all.