Page 2:Getting To Know Internet Explorer Again
Page 3:Test System Specs And Setup
Page 4:Performance Benchmarks: Startup Times
Page 5:Performance Benchmarks: Page Load Times
Page 7:Performance Benchmarks: Peacekeeper, Dromaeo DOM, And Acid3 Speed
Page 8:Performance Benchmarks: HTML5
Page 9:Performance Benchmarks: Adobe Flash
Page 10:Performance Benchmarks: Java And Silverlight
Page 11:Efficiency Benchmarks: Memory Usage And Management
Page 13:Final Results: Placing
Efficiency Benchmarks: Memory Usage And Management
This page ends our performance-based benchmarks, which used to make up the entirety of the WBGP. Now we'll switch gears and look at efficiency; specifically, memory efficiency.
We open each browser with just one tab, in this case Google.com. We then wait five minutes and record the memory usage numbers from Windows Task Manager. We then open 39 more tabs (the rest of the Quantcast Top 40), wait five more minutes, and again record the memory usage. These first two figures give us an idea how much system memory each Web browser uses, one with a full load of tabs, the other at near idle.
Microsoft's new creation steals the show, consuming only 18 megabytes with a single tab. Previous efficiency champ Chrome drops to second place, using 27 megabytes. Always good for light systems, Firefox only uses 40 MB. Opera ties up just over 50 MB, while Safari hogs almost 100 megabytes.
Firefox is again the most frugal Web browser for memory usage under heavy load, utilizing only 256 MB to display 40 tabs. Apple's Safari comes in second, employing 800 MB of system RAM, while Opera uses 850 MB. Both Chrome and Internet Explorer 9 use the most amount of system memory to fully load 40 tabs. Chrome uses just shy of one gigabyte, while IE9 uses 1.2 GB.
After we record the memory usage from the 40 tab load, we close 39 of the tabs, leaving only Google.com open. After five minutes, we record the memory usage to see how much system memory the browser gives back. Finally, we wait another five minutes to see if the overall memory usage continues to drop. After closing the browser, we again look at the total system memory to see if any of the applications hang onto or lose memory after being closed. This has not yet happened with any of the browsers tested in the WBGP.
-39 Tabs (5 minutes)
In another serious blow to the previous efficiency king (Google Chrome), IE9 uses less memory after closing all but one of the 40 tabs. Chrome still manages memory extremely efficiently though, holding onto only 42 MB after returning to a single tab. After five minutes, Firefox keeps less than 100 megabytes, a little more than twice the amount of memory before the extra 39 tabs were opened. Fourth-place finisher Safari keeps 330 MB, over three times its original single-tab total. Opera is weak in this area, keeping over 420 MB after closing all but one tab. That's over eight times the single-tab total.
-39 Tabs (10 minutes)
After an additional five minutes, Internet Explorer 9, Chrome, and Firefox remain in the same order. Safari also remains the same, though Opera drops down to 330 MB, beating Safari for the number four spot. At 330 MB, Opera still holds six times the memory of its single-tab load. Safari keeps three times its single-tab load, while Firefox doubles its usage.
Only Chrome and IE9 take memory usage down to less than twice their original one-tab totals, which are already the lowest of the bunch.
- Getting To Know Internet Explorer Again
- Test System Specs And Setup
- Performance Benchmarks: Startup Times
- Performance Benchmarks: Page Load Times
- Performance Benchmarks: Peacekeeper, Dromaeo DOM, And Acid3 Speed
- Performance Benchmarks: HTML5
- Performance Benchmarks: Adobe Flash
- Performance Benchmarks: Java And Silverlight
- Efficiency Benchmarks: Memory Usage And Management
- Final Results: Placing