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:
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.
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:
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.
105 Comments
View All Comments
Lifted - Thursday, February 1, 2007 - link
That's odd. I can search network drives using XP Pro. Maybe it's a Pro vs. Home issue?
Was also wondering about the network test myself. 10MB/s file copy on XP Pro seems abysmally slow when using gigabit NIC's. Just testing right now I about 35MB/s between a pair of 5 year old servers (dual Xeon 1GHz) with Intel GB NIC's. I haven't checked transfer rates with XP as I'm on a 10/100 switch at the moment, but I can't believe it's really THAT much slower than 2003.
Aikouka - Thursday, February 1, 2007 - link
I remember running a gigabit cross-over (CAT6) cable between my roommate's computer and my computer in college. We achieved about 33MB/s (through FTP) running Windows XP Professional on each. So I'd say that you'd probably see about the same speed if you were running a gigabit switch.mjz - Monday, February 5, 2007 - link
i think windows xp sets a limit when downloading from another computer to 33MB/s..Nehemoth - Thursday, February 1, 2007 - link
Same here.I just wanna Vista for the improve TCP/IP Stack, now I'll wait for SP1
tallsummi - Thursday, February 1, 2007 - link
I'll wait for SP2 of vista and then go for it..keitaro - Thursday, February 1, 2007 - link
Perhaps Microsoft should have copied the idea from Novell's SUSE Linux Desktop (powered by XGL and compiz). The compiz software package (compositor and window manager) comes with its own alt-tab that surpasses Flip 3D in every way. http://www.novell.com/products/desktop/features/xg...">See here for a look at what XGL and compiz can do.mlambert890 - Friday, February 2, 2007 - link
I think that xgl crap is an overenginered waste that adds 0 productivity. Flip 3d gives you the one thing you need - a live shot of running apps. Who the hell needs some spinning cube? And look how bad video playback perf is in that Novell demo...bleh... I dont feel myself drawn back to 1992 when I lived and breathed Novell; sorry...
Locutus465 - Friday, February 2, 2007 - link
I dont' know, personally I like flip 3d better..archcommus - Thursday, February 1, 2007 - link
The article makes me a bit sad about Vista. It made me realize - wow, yeah, it really IS a shame that Vista doesn't totally smash OS X Tiger given how long it's been in development and how long Tiger has been out for. I guess they just got in such a rut of catch-up that not many new revolutionary features could be developed.In particular, I'm disappointed with how similar (and ugly) certain aspects of Vista look compared to XP, for example the quick launch area, system tray, clock, and the overall taskbar. With the exception of the Start buttion being replaced by an "orb," it looks EXACTLY the same as XP, and this could have been and should have been revamped to improve productivity. Quick launch is just...stupid, and ugly. All it is is additional shortcuts, and they waste taskbar space. I think a small menu that appears and disappears on the fly would be nicer. I'm not sure what improvements to suggest for the taskbar, all I know is, with how pretty the rest of the OS looks, the application blocks down there just look out of place. Same with the system tray icons.
Explorer is better though and the transparency is great. It's too bad x64 performance and drivers aren't up to snuff yet.
thebrown13 - Thursday, February 1, 2007 - link
Microsoft has to cater to about 349852395472039 more software programs.That's why. Updates, bug fixes, feature designing, it all takes A LOT longer than with an OS with 5 people that use it, like Apple.
We're lucky the mainstream OS isn't MUCH farther behind.