Gateway NV52 (AMD) - OS Benchmarks
The final aspect of operating system performance we want to look at involves common OS tasks. We measure how long it takes to perform the routine operations of booting, shutting down, hibernating, resuming, suspending, and waking your computer using the four test operating systems. Unlike other test results, there was a huge degree of variability in some of the tests. We ran each test at least five times, and we took the best result - the reason being that some of the results were completely out of line with the average result, so including one or two results where the system took four times as long it didn't seem logical. Ubuntu and Windows 7 didn't show as much variation as XP and Vista, particularly in the sleep/wake testing, but the hibernate/resume test once again varies quite a bit between test runs.
The variability remained even after following a relatively straightforward test procedure. First we booted each laptop using the test OS (timing how long it took). Then we let the system stabilize for at least 15 minutes, with no extra applications running and the system sitting idle at the desktop. Finally, we performed one of the other tests - shut down, hibernate/resume, or sleep/wake. Obviously, you can't test resume time without first hibernating, and you can't test wake time without first putting the system to sleep, but otherwise we made sure to shut down the system between test runs.
We also need to mention that Windows XP has an inherent advantage in the hibernate/resume testing because we are using a 32-bit OS instead of a 64-bit OS. That means the system doesn't make use of all 4GB of memory, and the hibernation file is 3GB. Writing 3GB of data will obviously be easier than writing 4GB of data, especially when you're dealing with a 5400 RPM laptop hard drive.
The results are rather scattered this time, with certain functions favoring one OS and others looking better on a different OS. Boot times favor Windows XP, followed by Windows 7 which takes 11% longer. Vista trails Windows 7 by 10%, and Ubuntu brings up the rear at 5% longer than Vista. Shutdown times are a different matter, where Ubuntu takes the lead. Vista and Windows 7 are essentially tied, taking 55-60% longer to shut down than Ubuntu. Windows XP brings up the rear this time, at over 2.5 times as long as Ubuntu, although we have to say that this appears to be a driver issue as the result for the NV58 is radically different. When you shut down Windows XP on the NV52, there's a delay of about 15 seconds where there is no apparent activity, after which the hard drive activity light begins blinking. It would seem that without that handicap, Windows XP would be roughly the same as Vista and Windows 7.
As already stated, Windows XP 32-bit has an advantage for the hibernate/resume testing because it doesn't have as much addressable RAM. It ends up walking away with the hibernate/resume performance crown, followed by Windows 7. That said, the time to hibernate in Windows 7 is 34% longer than Windows XP and resume time is 32% longer; Win7 has 33% more memory, so a 32-bit version of Windows 7 ought to be as fast as Windows XP (or a 64-bit XP as slow as Win7). The gap between Windows 7 and Windows Vista is extremely large for hibernation time, with Vista taking 65% longer to hibernate and 46% longer to resume. Ubuntu is almost tied with Vista on the hibernation time, but it takes 50% longer to resume - about twice as long as Win7 - making it by far the slowest OS for this particular test.
We need to take a moment to discuss boot times and resume times, however, as there's more going on than meets the eye. When booting or resuming a system, the computer needs to perform a Power On Self Test (POST). That takes around nine seconds on these Gateway systems, and once that's complete the boot loader is activated which then loads the OS. Ubuntu uses GRUB and that appears to add an extra ~10 seconds relative to Windows. Without that time penalty, Ubuntu would be far more competitive in boot time (about equal to Win7), although it would still be in last place in the resume test. There are also laptops that have a fast boot feature so that they don't perform a lengthy POST, which can shave another 6 or 7 seconds off the boot/resume times. This is definitely a feature we would like to see implemented on more systems going forward, particularly laptops where users routinely boot or resume several times per day.
Wrapping up the OS performance analysis, the sleep/wake times were highly variable on the Windows XP and Vista operating systems. This is especially true if you put the system to sleep right after waking it up, booting, resuming, or any other complex task; in those cases, it might take over a minute to go back to sleep. Ouch! It may also take over 20 seconds for Windows to go to sleep if you have a bunch of applications open - that's about six times as long to put your laptop to sleep, which can be very annoying if you just want to pack up and go. You might think that you can just put your system to sleep and throw it in its bag and walk off, but sometimes a glitch will prevent a laptop from going to sleep so we like to make sure our laptops actually shut off before putting them in an enclosed space. We have heard of a few instances where a laptop has apparently overheated because it didn't go to sleep and a user put it in a laptop bag, resulting in a dead system. That's some food for thought anyway. Ubuntu and Windows 7 did a lot better, with the worst-case result being around twice as long as the best time.
Sleep times are a tie between Ubuntu, XP, and 7 at just under 5 seconds. Vista took noticeably longer even in our best-case result, trailing XP by 59%. Wake times mix things up quite a bit and show a lot less variation between runs, with Ubuntu falling to dead last and Vista and 7 essentially tied at ~3.5 seconds. XP takes 46% longer than Vista to wake and Ubuntu is 55% longer than XP (over twice as long as Win7). Again, though, variability in sleep times makes us prefer Windows 7 and Ubuntu followed by XP, with Vista being the worst at consistently going to sleep without a large delay.
106 Comments
View All Comments
Kibbles - Tuesday, September 22, 2009 - link
If all you have is a killawhat meter then that'll be pretty inaccurate. Not just because of the 1W accuracy but also measuing at the outlet you are also including the inefficiency of the powersupply.However I do agree that using the battery is throwing an extra variable into your equation. How big is it? I don't know. But I do know they don't always charge to the same capacity, and their capacity changes overtime.
I don't know if it's possible, but I would think the best option would be to have a DC source modded into the battery connection. Then measure the #W-h used. You would probably need a good variable DC supply and voltmeter to do this (maybe borrow it from the powersupply setting team?). Even then I don't know if you can do that, I think my laptop has like 6 pins on the battery. There's probably some connection for charging, some for battery status, and then the discharge connections.
The second option I see is putting a voltmeter on the DC-out side of the powersupply going into the laptop. You could run the benchmark without the battery for an equivalent duration and see if the W-h is close.
n0nsense - Tuesday, September 22, 2009 - link
Power savings in Ubuntu are far from optimal.I was more than surprised to see that even very basic features may or may not work.
For example on my Gentoo box each core frequency scaled separately.
On Ubuntu some processors are not supported. After all I thought that engineers at Canonical have better kernel understanding than me.
As for the tests, dim option is helping with battery life.
I don't remember such difference in battery life from my experience. Both Linux and windows where capable of ~3Hr on my laptop.
From my very personal point of view, Ubuntu is sluggish. I compared Ubuntu, XP, 7, Debian and Gentoo performance on IBM X31 with 1GB ram.
It started without Gentoo (It takes a while to setup fully optimized Gentoo box). Ubuntu and 7 where (IMHO only)the slowest. Debian and XP where just fine. But since I wanted more, i did the Gentoo thing. It was more than worth it.
With Ubuntu it was overall sluggish feeling (some tests will show much better performance under it than in windows). But feeling is important when you use something. Even more important than some numbers.
7 ... Same sluggish Vista with facelift and few tweaks that can be manually done.
Watching icons drawn few seconds after menu displayed was more than enough. It is more stable, can work longer without reboots, but nowhere faster than XP.
Debian with Gnome was nice so was XP. Anyway I'd stay with Linux since it's more customizable and have few useful things that make me feel handicapped in Windows.
Gentoo once again convinced me that it worth each second (it took more than 2 days on X31. should be much faster on any dual/quad core CPU and/or using distcc). But, not everyone can do it. Even "experienced" Ubuntu/Fedora/Suse (or whatever mainstream distro) may find that his understanding of "how staff works" is not on the required level.
Anyway it's quiet a change to see Linux participating in review.
Good job guys :)
lordmetroid - Tuesday, September 22, 2009 - link
I'll be running Arch Linux on my nettop, I tried gentoo 4 years ago from stage 1 and that was a nightmare to get installed. Maybe I should try it again but Arch Linux seems to be more interesting at this point as it had many of the packages I want in its repositories that I couldn't find in gentoo.stmok - Tuesday, September 22, 2009 - link
Running Arch Linux here on my ThinkPad T43...Much better than Ubuntu.Ubuntu feels bloated. Heck, even Xubuntu feels bloated.
void2 - Tuesday, September 22, 2009 - link
30..40 seconds to boot WinXP on modern CPU? That's sad. I get 7..8 seconds (boot menu to desktop, add your machine POST time yourself) on a comparable CPU (Athlon 64 X2 3800+). Clean OS, no SSD, no messing around with disabling services etc. How? Use Boot Cooler (www.bootcooler.com). It is free.lyeoh - Tuesday, September 22, 2009 - link
Why should anyone use bootcooler? The website doesn't even say what the program is _supposed_ to do, and how it achieves it. I don't see much on the web that describes or tests what it _actually_ does (as opposed to just claims), the limitations etc.It could be a trojan for all we know.
void2 - Tuesday, September 22, 2009 - link
If you haven't noticed, the website is under construction. Detailed explanation of how Boot Cooler works is included in readme.txt (in short - disk reads prefetching). And of course there are no reviews yet - the project is still in beta.orionmgomg - Tuesday, September 22, 2009 - link
I love antech - waiting for the radeon hd 5870 info to hit - looking at this artical - something about your battery lasting longer on your lap top...WHO CARES!!!
Give me a brake - you spend so much time on analizing minutes of extra juice it a fly is in the room or not! WHO CARES?
Plug your lap top in the wall - dont expect it to last any longer than it does when you have a full charge and it runs out of juice.
Once you know how long it lasts - realize your screwed - or should I say attached to the power cord!
Oh - did I mention - who cares?
Thanks for all your other articals!
orionmgomg - Tuesday, September 22, 2009 - link
I love Anandtech*^JarredWalton - Tuesday, September 22, 2009 - link
If you haven't figured it out, I'm the mobile reviewer at AnandTech, and my articles are about mobility. Writing articles about laptops doesn't mean I'm delaying any CPU or GPU reviews -- unless they happen to be mobile CPUs/GPUs. If you don't care about laptops, you don't need to read most of my articles, but please don't make the mistake of assuming no one cares. When people use a laptop on the road and don't have a chance to plug in, articles like this are very useful. If you never use a laptop, great; some people do and that's my target audience.