The Benefits of XP-64

The ability to address more memory isn't the only change with XP-64. It may be the most immediately noticeable change, but there are other reasons for the switch. So what sorts of benefits will you see by the transition to XP-64? The following slide was provided as an outline of improvements.



We've already discussed the larger memory support, but other performance improvements are still present. X86-64 (which we'll use as the generic term to encompass both AMD64 and EM64T) doubled the number of registers from eight in the 32-bit world to sixteen in the 64-bit world. Depending on the application, the additional registers could help a little or a lot. Anand is still working on benchmarks, and the change in OS has brought quite a few difficulties for our benchmarking setup, but chats with a few vendors suggest that the additional registers should bring on average somewhere around a 7% performance boost. Again, that's just a guess, but it's important to remember that hardware designers and compilers have been working around the idiosyncrasies of the x86 architecture for several decades now, and with techniques such as register renaming, additional registers aren't going to bring massive performance boosts in most scenarios.

Several of the bullets in the slide are essentially just filler material; we've heard many times about how the latest OS provides better productivity, a great platform for new software, and improved reliability. Sometimes we see those features, sometimes we don't; only time will tell. The enhanced layer of hardware protection is actually present, via the XD/NX (execute disable/no execute) bit that Intel and AMD provide in their latest processors. How successful that feature becomes - it's already enabled in XP SP2 - is still up for debate, however.

At this point in the keynote, Microsoft began to give some specific examples of the performance benefits that were possible with the shift to 64-bits. We remain somewhat skeptical in some instances, but there are definitely areas that stand to benefit. The first demonstration was of NewTek's LightWave 3D rendering software, comparing the 32-bit and 64-bit versions. We tried to take some shots, although they are blurry and dark at best.



The presenter, Jay Kenny, gave some example interactions and suggested that model complexities could be increased substantially with the 64-bit version. He stated that certain complex scenes that would have required 100 passes in the 32-bit version could be done in as few as 7 passes in the 64-bit version, although it appears that each pass took longer in the 64-bit version as the average speedup was claimed as around 3X. Another example given was the ability to work in more completely rendered environments rather than flat shading models, although we're not entirely sure what constraints prohibited the 32-bit version from using textures.





The next example given was of SQL Server 2005, once again running 32-bit and 64-bit versions on the respective OSes. The hardware was supposedly identical, but as you can see in the slides, the 32-bit system reports 1 GB RAM and Page File sizes while the 64-bit system reports 2 GB RAM and Page File sizes. Our impression was that there were some smoke and mirrors present, but we would still expect a large database to have substantial performance benefits by running in a 64-bit world. The demonstration showed CPU usage spiking to 100% rather rapidly in the 32-bit world, while the 64-bit world was able to handle 5X as many clients at a lower total CPU usage.



After the demonstrations, we were shown the above list of current 64-bit solutions being offered by Microsoft, as well as their plans moving forward. Not surprisingly, all of the solutions MS is focusing on are related to the server environment. MS is more dependent on 3rd party support for the desktop applications that can benefit from 64-bits, and now that XP-64 is officially released, we should see these products begin to show up at retail.

How Much Memory Is Enough? Beyond XP-64
Comments Locked

36 Comments

View All Comments

  • PrinceGaz - Tuesday, April 26, 2005 - link

    from page 3 "...and with the largest readily available DIMMs currently coming in at 2 GB in size"

    in reply to #5, #6 - Crucial have had 4GB PC2100 DIMMs available for purchase from their website for quite some time. They're certainly not cheap, but they are readily available. If you've got the cash I'm sure they'll sell you a few dozen of them.
  • DerekWilson - Tuesday, April 26, 2005 - link

    MS may have needed to restrict 64bit to long longs due to some internal operating system code issues ... If, in fact, linux distros that run on x86-64 impliment 64bit longs this may be the case. Otherwise I'd lean towards a hardware issue.

    At this point I haven't looked into it, but I will be sure to ask around (as this is surely the place to do it).
  • bobsmith1492 - Tuesday, April 26, 2005 - link

    Melgross - is that English?? I read it over real quickly and it was like... dude, what's he talking about? It just took a good close look though. :P
  • melgross - Tuesday, April 26, 2005 - link

    MS wants to control whatever they can. Control graphics memory and we are another step towards commoditized graphics boards.

    I wonder why MS went the way they did with the 64 bitness of the system. They went to (LL)P64 where just the long longs and the pointers are 64 bit, rather than LP64, where the longs are also 64 bit.

    They are the only ones to do that. It seems like a half measure. A conversion from any Unix distro (or OS X) would need more work than is good, as well as a lessening in it's effectiveness as a 64 bit system. Are the 64 bit extentions of the x86 chips at fault?
  • JarredWalton - Tuesday, April 26, 2005 - link

    Okay, the typos are fixed, and those that didn't like the 8-bit PNG graphics should now be happy. Iit was 4:30 AM when we finished, so our judgement was a bit impaired.) Just don't complain about how the PNGs are now five times as large. :)

    My personal opinion is that Windows XP removed most of the problems with the Windows platform. We'll see how Longhorn works out when it gets here, but that's still almost two years off. The graphics effects are nice, but pretty much totally unnecessary. Hopefully, we'll see some true improvements in the overall performance and not just eye candy.
  • Googer - Tuesday, April 26, 2005 - link

    Linux on a MAC: Total freedom from with in a confined space.
  • DerekWilson - Tuesday, April 26, 2005 - link

    tbh, with the current state of things Linux game performance is not up to par with windows. Even with windows managing graphics memory, windows performance will likely be better.

    And from a workstation perspective, having virtualized graphics memory for free is more of a blessing than a curse.

    I do think it would be better if MS gave graphics developers a choice whether to allow windows to manage graphics memory or not...
  • Son of a N00b - Tuesday, April 26, 2005 - link

    dont you dare go screwing up the performance of my vid card ms...if you do im going linux...
  • suryad - Tuesday, April 26, 2005 - link

    Agreed. Windows should not be managing graphics ram...unless MS came up with some new techniques...MS seems to be pulling out all the stops though in my opinion. I think the hybrid drive is a good idea but like #12 said...that is quite a concern!
  • Cygni - Tuesday, April 26, 2005 - link

    #10's post makes me giggle.

Log in

Don't have an account? Sign up now