What Really Slows Windows Down
Page 1: Introduction
The follow up experiment testing more software with improved benchmarks. If you want to know what applications are slowing down your machine, check out this post.
Preamble
A week ago, I performed a study demonstrating how certain applications can slow down Windows. If you didn't catch it, I'll sum things up now.
I took a clean Virtual PC install of Windows XP Pro (SP2a) and installed Microsoft BootVis on it. For those not in the know, BootVis is a tool that lets you time how long windows takes to start up. It does a lot more, but I wasn't interested in any of that for the experiment. I've had a lot of feedback via email over it: mostly praise and suggestions for the next round-up.
Lots of people complained about me using Virtual PC. The reason I chose it at the time is because I know from experience that VMWare is about 1000times heavier on the host OS. It installs drivers and system services all over the place and is generally unpleasant unless you need to use it all the time.
Most of the suggestions that filtered into my inbox were for other antivirus systems. I've added a bevy of different applications and I've also re-benched Norton InternetSecurity, considering this did worst of all the applications tested last time. Searching on places that the old article got linked from, I saw that Norton got quite a bad (but not unexpected) deal, so I wanted to make sure that this wasn't unjust.
The Host System
Some people also commented that it would make more sense if they knew more about the physical setup I've been running the tests on. So for them, here's what my PC is:
- AMD 64 X2 4800+
- 2Gig DDR RAM
- 2x 36Gig WD Raptors in RAID0 (system OS)
- 2x 120Gig Seagate Barracudas in JBOD (one for VM, other as the scratch disk)
- 3x 300Gig Maxtor DM10s in RAID5 (nothing to do with any of this =])
The more astute will have noticed that I've got two cores (effectively two processors). For both the experiments I set the affinity of all the host OS programs to one core and set the VM onto the other core. The VM also had 512megs (of 2048) RAM dedicated to it. I also used two HDs for the system. One was a read only base-image of Windows and the other was used as the "scratch" disk – in short where all the changes were made.
There were also a lot of people saying that the figures I was providing did not reflect accurately on what really slows windows down. I think that's slightly fair although it's also a fair assumption that if something is bogging down the start up, it's going to continue its reign of terror all the way through your lovely Windows session.
Pages
- Introduction
- The New Benchmarks
- Norton Internet Security 2007
- The Contenders
- Results and Conclusions
Don't just sit there like a lemon! Reply!
Got something to say? Now's the time to share it with the author and everybody else that reads this posting! Lemons need not apply.