Microsoft's IE8 Beta 2 hogs memory, says researcher
'IE fatter than Windows XP,' uses twice as much RAM as Firefox in browsing tests
Computerworld - Editor's note: The person quoted in this story as "Craig Barth" is actually Randall C. Kennedy, an InfoWorld contributor. Kennedy, who presented himself as the CTO of Devil Mountain Software, no longer works at InfoWorld. Given that he disguised his identity to Computerworld and a number of other publications, the credibility of Kennedy's statements is called into question. Rather than simply remove stories in which he is quoted, we have left them online so readers can weigh his data and conclusions for themselves.
Microsoft Corp.'s latest beta version of Internet Explorer 8 requires more than double the system memory of its main rival, Mozilla Corp.'s Firefox, and spawns nearly six times the number of processor threads, a performance researcher said today.
IE8 Beta 2 also consumes 52% more memory than IE7 and uses almost three times as many threads, said Craig Barth, chief technology officer at Devil Mountain Software Inc., a Florida-based maker of PC performance testing software.
"IE8 is epically porcine," said Barth. "Microsoft has gone to epic levels of bloat."
Barth tested IE8 Beta 2, IE7 and Firefox 3.0.1 in a 10-site scenario that involved media-rich domains such as boston.com, channel9.com, cnet.com, infoworld.com, nytimes.com and others. Each site was opened by each browser in a separate tab, then links on those sites were opened in new tabs. Both Flash and Microsoft's Silverlight were installed as plug-ins for each browser.
By the end of the test, IE8 Beta 2 had grabbed 380MB of memory on the 2GB-equipped system running Windows Vista, while IE7 consumed 250GB and Firefox 3.0.1, the most-recent version of the open-source browser, had taken 159MB. When the same tests were run under Windows XP, each browser consumed slightly less memory than it did with Vista; IE8 Beta 2, however, continued to lead the competition by wide margins.
"When Windows XP starts, the entire OS takes 130 to 150MB," said Barth. "Suddenly you're looking at a memory footprint for IE that's bigger than Microsoft's earlier operating system. IE8 is fatter than XP."
When Barth tallied up the separate processor threads each browser spawned during the tests, he also found that IE8 Beta 2's count was dramatically higher than either IE7's or Firefox's. The latter, for instance, never used more than 29 concurrent processor threads during the 10-site test, while IE7 spawned a maximum of 65. IE8 Beta 2, however, used a whopping 171 threads.
Piling on the threads, said Barth, "becomes overwhelming after a while," and it can have a direct impact on the speed of the browser. The more concurrent threads, the more operating system overhead managing those threads, and the more the processor is stressed. Web browsers typically use multiple processor threads, but when the thread count climbs, performance can suffer unless the application is running on a multiple-core processor.
- Six Ways Your Small Business Can Save with Internet Phone Service Traditional phone systems present two main problems for businesses: limited features and high costs. As a result, small businesses are migrating to Internet...
- Face Time Anytime Real-time communications facilitates team collaboration from nearly anywhere in the world. With facts and figures you can use to justify an investment
- Now is the time to implement a video conference solution Video conferencing is getting a lot of buzz lately due to the recent cost decrease, making it tangible for many law firms. It's...
- Video drives engagement Achieving maximum results means building a solid platform and network infrastructure. As digital age unfolds, it's clear that the ability to communicate effectively...
- Cloud Knowledge Vault Learn how your organization can benefit from the scalability, flexibility, and performance that the cloud offers through the short videos and other resources...
- LIVE EVENT: 5/7, The End of Data Protection As We Know It. Introducing a Next Generation Data Protection Architecture. Traditional backup is going away, but where does this leave end-users? All Web Apps White Papers | Webcasts