Where does 64-bit help?

Although the performance that will sell the Athlon 64 today has nothing to do with this, the 64-bit part of the equation will definitely play a role in the processor's future. With no final release of the 64-bit version of Windows XP, there is no popular OS support (we will touch on Linux support as well as Win64 support shortly) and no real application support at this time, but where will the 64-bitness of the Athlon 64 help?

There are three main categories that you can split up the performance benefits into: 32-bit applications running on a 32-bit OS, 32-bit applications on a 64-bit OS and 64-bit applications on a 64-bit OS; we will be analyzing each one of these scenarios individually.

Case 1: 32-bit apps under a 32-bit OS

At the launch of the Athlon 64, the predominant operating environment will be running 32-bit applications under a 32-bit OS. All performance benefits the K8 architecture will show here are courtesy of the on-die memory controller, improved branch predictor, higher clock speed and more robust TLBs - none of the performance improvements you'll see in this case will have anything to do with the 64-bit capabilities of the processor.

Case 2: 32-bit apps under a 64-bit OS

When Windows XP 64-bit Edition is officially released (a public beta is due out at the time of publication), many users will be running their 32-bit applications under the 64-bit OS.

Outside of the performance improvements that we just outlined in Case 1, there are a couple of additional benefits the Athlon 64 may offer users. Currently under Windows, although you have a physical memory limit of 4GB, any given process can only use up to 2GB of memory; the remaining 2GB is reserved for use by the OS. With the 32-bit applications under a 64-bit OS scenario, each 32-bit application could be given a full 4GB of memory to work with, instead of being limited to the 2GB Windows process size limitation. Unfortunately this benefit isn't really "plug 'n play" as the application would have to be aware that it can use the added memory, which in the vast majority of cases would require a new patch to be made available.

The second benefit the Athlon 64 could offer in this scenario comes from the availability of additional registers. Although the 32-bit application would still only be compiled to use the regular set of 8 general purpose registers and standard set of FP and SSE2 registers, the 64-bit OS would be able to reference and use all of the registers at its disposal. The performance benefits that you would see here exist in any sort of task handling that the OS would be doing (switching between applications) as well as just regular Windows performance. Granted that the performance improvements seen here should be negligible, considering the extra overhead that does exist when running 32-bit applications in a 64-bit environment (more on this in a bit).

Case 3: 64-bit applications under a 64-bit OS

The final scenario is the one that shows the most promise, yet has the least amount of application support today - running a 64-bit app under a 64-bit OS. Here, the benefits are numerous; not only do you get the performance improvements courtesy of the Athlon 64's architecture, but each application now has full access to the increased number of registers and each application can use much more than 4GB of memory.

Although the Athlon 64 can support 64-bit memory addressability, for demand reasons it only supports 40-bit of physically addressable memory - or ~137GB, not exactly a limiting factor at this point.

The performance improvements developers are expecting to see under this final scenario has been estimated to be in the 10 - 20% range in tasks that are not memory bound, meaning those areas where the application is using less than 2 - 4GB of memory in the first place will still see sizable performance gains courtesy of the availability of more registers. We will investigate a few of these scenarios to substantiate (or refute) these claims later on in the article.

Performance improvements where you are memory bound will be even more impressive; just think about how slow swapping to disk is and how much faster keeping everything in memory makes your computer.

An Early Christmas present from AMD: More Registers AMD's Gem: Athlon 64
Comments Locked

122 Comments

View All Comments

  • Anonymous User - Wednesday, September 24, 2003 - link

    Nice review anand, however I am missing the P4 EE in a number of the tests, as previous post (#67) suggested.

    The Athlon 64/A64 FX appears to be a nice processor, for a shiny new design cpu the advantages were expectable.

    Some more 64bit tests, maybe a divx codec pre-compiled for 64bit in a test?

    As for the amd vs intel combat:
    The A64 and A64FX match up a lot better against the latest p4/p4EE. I wouldnt have expected anything else.
    While the prescot still lurks in the dark and I have a feeling Intel has something up their sleeve I wouldnt call the prescot an failure yet.
    If Intel plays nicely along, maybe they can create a cpu that beats the A64/A64FX in 32 (and just maybe in 64bit http://www.theinquirer.net/?article=11668).

    Either way, the more AMD and Intel compete each other, the happier I am, after all I end up paying less for either cpu.
  • Anonymous User - Wednesday, September 24, 2003 - link

    There is already a 64 bit port of America's Army available that doesn't need a 64 bit OS! http://www.amd.com/us-en/Corporate/VirtualPressRoo...
  • Anonymous User - Wednesday, September 24, 2003 - link

    Guys, if the AMD Athlon 64s don't succeed, I believe AMD would go under or be in financial trouble. So these new processors MUST sell well.
  • Anonymous User - Wednesday, September 24, 2003 - link

    I'm curious why RedHat Taroon, which is an enterprise-focused Linux distribution, was used for the 64-bit benchmarks and not RedHat GinGin64, which is more consumer-focused. Both are available from the RedHat FTP site.
  • Anonymous User - Wednesday, September 24, 2003 - link

    Several of the benchmarks left out the P4 Extreme scores (memory bandwidth, Content Creation 2003, and Virtual Studio 6.0 Compile) - was that a mistake or benchmarking per AMD's new guidelines? It's also funny that this is one of the first Anandtech CPU reviews without the full system specs documented (i.e. ECC memory vs non ECC, Intel branded motherboard vs. ASUS enthusiast motherboard, memory latency settings, etc.) - more AMD review guidelines?

    The way I see it, you can either spend the money on a whole new Athlon 64/FX CPU, motherboard, and memory outfit, or buy a P4 EE and stick it into any motherboard today that accepts a 3.2 GHz CPU - that sure beats having to buy a new motherboard and memory to get about the same level of performance average across the board.

    Even when 64-bit Windows comes out, does everyone really think that Microsoft and Bill Gates will really make it priced at mainstream levels and reduce the cost of the current 32-bit Windows XP so soon? I have my doubts but I guess we'll just have to wait and see.

    Another interesting thing to note from Tom's Hardware review is that the 64-bit code for AMD64 does run faster on 64-bit OS but if you read carefully, he says that the same program optimized for the P4 runs even faster on 32-bit OS. So, software companies will probably have to make a choice (unless they are big enough and make enough money to serve all markets): A - optimize 32-bit software to take advantage of the P4/Prescott and Hyperthreading using compilers that Intel provides, or B - compile 64-bit software for which there is still no mainstream OS and there are hardly any standard compilers available for and market them to the 500,000 or so people who will have the opportunity to own AMD64 desktop chips this year.

    Sure Intel has a problem with the Prescott heat dissipation right now but I don't think they will be sitting idle. Thermal interface technology is getting better all of the time and I wouldn't doubt if Intel isn't already making process improvements and/or implementing newer cooling methods. After all, it was Intel who came up with the heatspreader design for the current generation P4 that is now being used by Hammer chips.

    Once the Prescott on .09-micron technology hits the streets it will continue to be refined and improved upon so the clock speed will continue to increase. Imagine a Prescott EE CPU with 1MB L2 and 2MB L3 or more. What would be a real thorn in AMD's side would be if Intel makes a shrink of the current P4 onto the new .09-micron technology and increases the clock speed to the 4 GHz level (already achievable by some CPUs on the current .13-micron process) to keep pace with the Athlon 64/FX which is supposed to be AMD's next generation CPU. They could put a whole bunch of P4 die (even P4 EE die) on a 300 mm wafer and put a hurting on AMD until they can get their 90nm process and 300mm wafer process going. It is a scary possibility for AMD but could be reality for Intel - meanwhile, AMD still has to face the daunting task of converting to 300mm wafers and 90nm process at the same time to keep up. AMD says that they will start 90nm production in the first half of 2004, but then again, they've been promising hammer since 2001. But they have to do something because with their current situation of roughly 192 square millimeters per Athlon 64/FX die on a 200mm wafer yields a theoretical 73 die per wafer (per Tom's Hardware review). And I believe that AMD wants to put all of their products on the same line and differentiate them at the end - similar to the way Intel does with their Northwood/Celeron products (same die with certain cache and other things disabled) - so even the 256K L2 cache mainstream Athlon 64 comes out, it may still be the same size as all of the other Athlon 64/FX/Opterons.

    Hector Ruiz, Jerry Sanders and AMD as a whole have a very steep mountain in front of them to climb. Time will tell if they have what it takes to get up and over it. The first checkpoint for them will come in about 3 weeks in the form of Q3 earnings. By then we'll see how sales of their new CPUs are going and if their joint venture in FLASH pays off. (It didn't really make sense to me for them to lay off 2000 people at the beginning of the year to reduce costs and then turn around 2 quarters later and pick up 7000 people in the FLASH venture with Fujitsu which comes with more debt than earnings.) I'm not a betting man, but if I were, my money would be on AMD making 9 straight quarters of losses in a row. When Hector Ruiz came to office he vowed that AMD restructuring would make them hit break-even sometime around Q2 2003 but that never happened. There seems to be a pattern with promises made by AMD. I guess it's why his 3 million stock options which were granted at $16 are still under water.
  • Anonymous User - Wednesday, September 24, 2003 - link

    Apparently the FX series is unlocked multiplier, and mobos will be coming shortly that have multiplier selection options (read Anand's "weblog" entry)... I can't wait to see the results of a 13x 220 FX-51; now, THAT I might part with $800 to play with... Talk about insanely fast processors, the higher FX goes, the smaller Intel's lead gets.
    Whoever said that throwing more cache on the P4 core beat Hammer is just deluded; P4 is at the end of its line, AMD64 is just beginning. And once again, Intel supporters seem to grow rather silent when you point out that the on-die memory controller becomes significantly more powerful when the clock speeds ramp up; a 3.3GHz FX chip would be more than a match for a 3.4GHz Prescott, I'd think. Memory bandwidth advantage is a thing of the past for Intel, now it's up to AMD to shore up their lacking SSE/SSE2 performance and work on speeding up the core, as well as meeting the demand for such upgraded processors.

    I'm not normally so pro-AMD (though I support their products more than Intel's, just from a cost efficiency standpoint), but it's kind of hard to not be wowed by the muscle this chip can flex. I mean, this is the Day One marketed "prototype" and it's capable of matching its most recent and mature rivals, can you imagine what next year is going to look like?
  • sprockkets - Wednesday, September 24, 2003 - link

    The fact that Intel HAD to release a EE edition shows desparation at looking behind. Yeah, so the Prescott does look good. That and the 103w dissipation, unconfirmed if it is on the 90 process, if it is then that's pathetic.

    I can buy a Athlon 64 or FX, where is the EE like others said? And why was the NDA lifted on the same day as the AMD Athlon 64?

    Complaining about price? The 1.5ghz P4 costed around $1000 when it came out and was slower than a P3 1.0ghz, while the new Athlon 64 always is faster than the XP.
  • Anonymous User - Wednesday, September 24, 2003 - link

    lmfao

    AMD is still the underdog :P Always will be. You get what you pay for.

    AMD is for the guys who love to root for the underdog; in otherwords fanboys. If you want solid, no hassle performance with top support .. you know where to put your money.

    I mean christ, Intel doesn't even have to design a next generation core to outmatch AMD's next core eveolution -K8- they just simply tack on more cache ;) How sad is that?

    AMD fans, take a hint ... AMD's STILL playing cat-up with Intel. Read the article closely, and you'll see what I mean -the author hints at it so clearly as well- Its so easy to see. AMD has never had the advantage ;) Only clever marketing which most people pin as bad marketing on AMD's part. Quite the contrary, Stupid kids!
  • Anonymous User - Tuesday, September 23, 2003 - link

    #61 ya I know how they compare...the g5 is a mac no software support and the cartoons might pop out of the screen and eat you.....no comparison....
  • Anonymous User - Tuesday, September 23, 2003 - link

    Which chip is faster at Divx encoding?

    http://www.anandtech.com/cpu/showdoc.html?i=1884&a...
    OR
    http://www.hardocp.com/article.html?art=NTI0LDM=
    OR
    http://www.aceshardware.com/read.jsp?id=60000256
    OR
    http://www4.tomshardware.com/cpu/20030923/athlon_6...

Log in

Don't have an account? Sign up now