Updated by HAL9000 | Raymond.cc
To summarize the results from all the browser’s RAM and CPU usage, here’s a simple table showing the scores. Green is obviously the best and pink is the worst for each category. Do note the “Peak CPU usage” is AFTER the pages have fully loaded and not while loading, all browsers hit 100% during that time.
The good points:
- Predictably Opera was the fastest to load and stayed low on CPU usage when viewing Flash rich pages, although the problems it still has viewing some webpages properly might put people off.
- A resource friendly surprise was GreenBrowser as it loaded fast, was low on memory and kept CPU usage to a minimum. The interface is not the best, but compatibility should be good as it uses the Internet Explorer Trident rendering engine.
- Firefox has improved a lot recently in resource usage, but few people run it without plug-ins so the memory usage and load time will likely increase when several are added.
The not so good points:
- Avant’s nice idea of 3 different switchable browser engines in the same browser sounds like a good idea, but needs a lot more work to make it fully optimized and really worth using.
- It’s not clear if Apple have discontinued Safari, but with it’s high memory usage in this test and terrible load time of the 10 test pages, I’m not sure why anyone would want to use it.
- High memory and CPU usage playing Flash meant Chrome surprisingly wasn’t great either, which is probably why they’re concentrating on these areas in future versions.
What the test does show is that overall it’s not a good idea to leave a webpage open on your machine with something like a Flash animation running for long periods of time, especially a laptop or netbook. As expected, CPU usage goes up greatly with any kind of Flash on the page, some browsers hitting 80% on a single processor core.
As many of the browsers use plug-ins or extensions to enhance them even further, this would affect all these scores greatly. For example, a Flash blocking tool would increase the browser’s used memory slightly, but load times and CPU usage would be reduced.
Read more: http://www.raymond.cc/blog/battle-of-the-browsers-in-cpu-and-memory-usage/#ixzz2c9knotjn