Tuesday, 15 May 2012

Sad And Pathetic Machines

On Saturday I visited a friend’s house to see if I could help them with slowness problems on their home computer. This was a six-year-old machine running XP with 448MB RAM. I observed that on startup Windows Update would run and while running, pretty much all the RAM in the system was consumed by Windows, wuauclnt.exe and svchost.exe (which assists Windows Update). During this time, starting Firefox or IE took minutes; the machine would thrash itself senseless. This state lasted for quite a long time, about half an hour, probably exacerbated by my attempts to get stuff done. Once it subsided, Firefox started quickly and ran well.

This is apparently a known problem and some kind of Microsoft regression.

Under these conditions, Firefox startup time and other metrics are bound to be awful.

Update I forgot to mention, but the Microsoft malware checker was also running at the same time as Windows Update and contributing significantly to resource usage. I guess it checks the downloaded and installed updates for malware...


  1. I filed https://bugzilla.mozilla.org/show_bug.cgi?id=684646 about detecting common perf suckers like this. UX/frontend people are not super excited about this, mainly because we do not have a way to report info like this in the UI.

  2. Yes, I've seen that kind of thing happening on my in-laws' computer running XP. Windows Update doesn't only suck up the memory, it also thrashes the disk drive quite heavily (particularly when creating a restore point). Which is very bad if you are trying to do something else at that moment.

  3. Indeed, it's a perspective a lot of us developers with blazing fast quad-core i7 machines with multiple gigabytes of RAM and SSDs lose.

    That Windows Update issue in particular is really sad.

  4. I've seen this happen on relatively new hardware on Windows 7. One contributing factor was that the user of said machine turned it off for days at a time. I don't think many of us ever turn off our machines.

  5. I only very recently inherited a new hand-me-down desktop. It replaces an old Dell (made in 2004) with a Pentium 4 processor and lots of other old kit. Testing nightlies with it often showed up problems that people with high-end hardware didn't see.

    An example of this is bug 509986 which was closed as WFM, but only because the person testing it was hitting the 60 FPS cap on newer hardware.

    I also agree with what Asa said. If a machine hasn't been booted for a while, every update service suddenly notices that the last update was > 7 days ago (for example) and kicks in. Windows Update, AV update, Adobe Reader, Flash, Java, Apple stuff, HP update / other vendor-specific stuff.

    Does Telemetry provide relevant data about hardware? I think total RAM is reported, not sure if CPU information is.

    Searching for Windows XP + single-core 32-bit processor might give a rough estimate for the number of these kinds of machines in use.