CPU Performance and Threading in Vista

While we found memory requirements in Vista to be greater than XP, CPU requirements weren't as much of a big deal. There are parts of Vista that will obviously benefit from faster CPUs, but if you have anything in the Core 2 or Athlon 64 X2 class you should be just fine. The argument for dual and quad core processors remains relatively unchanged with Vista. For multitaskers and many CPU-intensive workloads, a dual core CPU makes perfect sense. Vista doesn't make the argument for dual or quad core any more compelling than XP in our opinion; the additional background tasks that run in Vista that weren't present in XP don't really eat up that much CPU time to begin with, so dedicating an entire core to them isn't necessary.

The new applications in Vista don't appear to be any more threaded than XP, despite Vista being heralded as the beginning of a highly threaded future. Microsoft Word remains single threaded, although Excel can now take advantage of multiple cores when performing calculations. Windows Movie Maker seems to be optimized for two cores, while importing and attaching files in Photo Gallery is surprisingly single threaded. Dual core still makes a big difference in the overall experience, while quad core still isn't necessary but remains useful for a handful of situations.

With high definition video playback and encoding being two very big drivers of CPU performance and number of cores, Vista will be the OS under which new highly threaded applications really start to appear but there's no reason to feel like four cores are necessary to run Vista today. An interesting bit of trivia is that on a Core 2 Duo E6300, simply opening a new Explorer window in Vista will eat up about 19% of your total CPU time while the window opens and animates; turning Aero Glass off doesn't change the CPU usage either. Maybe four cores are necessary...

Vista Search for Fast Drives Only?

In our opinion the two biggest reasons to migrate from XP to Vista are its Search and SuperFetch technologies, as they both dramatically impact productivity. When Mac OS X introduced system-wide indexed search functionality, we wondered if disk performance would dramatically impact how responsive the search was. More specifically, would notebooks running OS X have significantly slower search times than desktops with faster 3.5" drives? Under OS X, while we noticed a difference between desktop and notebook drives, it wasn't large enough to render the feature crippled on a slower drive. Thankfully, the same can be said about Windows Vista.

We noticed absolutely no difference in how long it took indexed search results to appear whether we used a 150GB 10,000RPM Western Digital Raptor, our 500GB WD test drive, or even a 5-year old 100GB drive - the results were always near-instantaneous. In fact, a much larger impact on search performance was how much memory the system had. The less system memory you have the more disk I/O there's going to be due to swapping data in/out of the pagefile, and that I/O ends up reducing search performance tremendously. We noticed a much bigger search performance improvement going from 512MB to 1GB of memory than going from a 5-year old drive to a modern day, high-end 10,000 RPM Raptor.

While performing searches didn't show any difference between various hard drives, there is a noticeable performance difference between drives when it comes to how long it takes to index your drive if you should have to rebuild your index. The chart below shows the amount of time it took to rebuild Vista's search index on the three drives we've been using in this review:

Vista Search Index Performance

Obviously the larger the amount of data to index, the greater the impact drive speed will make on it, but this should give you a bit of a reference point. Of course all of the normal benefits of moving to a faster drive still apply (faster application launches, documents open quicker, games load faster, etc...), but the point we're trying to make here is that if you've got a reasonably fast drive already, don't feel like you have to replace it in order to keep up with Vista.

Networking Performance Synthetic Application Performance
Comments Locked

105 Comments

View All Comments

  • thebrown13 - Thursday, February 1, 2007 - link

    This is TOTALLY false. Microsoft allows content providers to do what they want with their content. Again, THE CONTENT PROVIDERS DECIDE WHAT THEIR CONTENT PLAYS ON. MICROSOFT DECIDES NOTHING.
  • MAIA - Thursday, February 1, 2007 - link

    The architecture is still x86 with 64-bit extensions. The correct naming should be 32-bit x86 and 64-bit x86. Although some vendors use the x64 "slang", this only serves to create more confusion, making people believe it's a different architecture. More, editors and reviewers should use the correct definitions, they also have an educating factor which have to live up by a good standart.
  • Ryan Smith - Thursday, February 1, 2007 - link

    It makes little sense on our part to use something different than Microsoft's own terminology here when talking about Vista. The x86-64/EMT64/AMD64 versions of Vista are all called Vista * x64, so we're going to be consistent on using Microsoft's naming to avoid possible confusion among Windows versions.
  • Myrandex - Thursday, February 1, 2007 - link

    Eh I don't know how x64 can get confusing, but x86_64 is pretty typical as well.
  • smitty3268 - Thursday, February 1, 2007 - link

    Actually, it is a new architecture that just happens to be backwards compatible with x86. That is why there are twice the number or registers available and not just the same amount doubled in size. You're right that x64 is not the correct name, (it's technically called x86-64) but what does it matter? Everyone knows what it means.
  • Gunlance - Thursday, February 1, 2007 - link

    I wish I could agree about the new installer. My experience with trying to boot windows vista so far is worse than when I learned how to put NetBSD on an Apple G3.

    In fact I am still trying to get into the Windows Vista setup as I type this comment. I have been up all night :( I simply just don't get it. Every OS I have ever put on my desktop at least boots, and the vista beta's installed fine. Ugh.

    The article was great! Heh. It has made me a bit more frustrated though. Because here I am with vista but still only being able to read about.
  • erwos - Thursday, February 1, 2007 - link

    Your OpenGL performance numbers are radically higher than what Tom's has. Could you comment on the drivers and installation that you used?
  • Ryan Smith - Thursday, February 1, 2007 - link

    Normally I tend to avoid commenting on anything involving competitors, but...

    Assuming I'm looking at the right article here, they were using the Catalyst 8.31.100.3.2.1 driver, which was released back in December. We were using the Catalyst 7.1 driver(version # 8.33.something). ATI did not include an OpenGL driver until 7.1(and just barely at that).
  • ktgktg - Thursday, February 1, 2007 - link

    I'm surprised that the article didn't mention how much ReadyBoost could lower the boot time. A member of notebooreview forums claimed that http://forum.notebookreview.com/showthread.php?t=1...">he lowered the boot time on a laptop (slower HD) from 80 to 43 seconds (including POST) with a 2 GB SD card. Remember that http://en.wikipedia.org/wiki/Comparison_of_memory_...">SD cards are slow compared to USB and CF. Although they're all slow compared to RAM, they have the benefit of storing the data until next boot.

    SuperFetch seems to be just another reason for using standby mode.
  • yacoub - Thursday, February 1, 2007 - link

    Any word on FireFox compatibility with Vista? That is, does it run just as flawlessly as it does under XP x86 and x64?

    Just wondering. The comment on the Conclusions page about IE 7+ being the new standard for Safari is what made me think to ask.

Log in

Don't have an account? Sign up now