'Heavy' Google Chrome is no less than IE8

Google Chrome also takes up more memory resources than Internet Explorer 8 Beta 2 - the most heavily considered browser version today.

That's confirmed by Craig Barth, CTO of Devil Mountain Software Inc, after a small test. Barth also tested and concluded that IE8 Beta 2 was "heavier" than IE7 and Firefox 3.0.1.

' Similar to IE8 Beta 2, I think Google Chrome also targets next-generation hardware, not older PC products using single-core chips and relatively limited RAM ,' he said. Barth said.

"Crash" RAM .

Google Chrome also has to go through the same test steps as what IE8 Beta 2, IE7 and Firefox 3.0.1. Specifically, this browser is also tested to operate continuously with 10 rich content websites such as boston.com, channel9.com, cnet.com . is opened on each 'card' (Tab) independently.

The goal of the experiment is to calculate the level of 'resource' of the system RAM memory and the level of utilization of the thread 'thread' - in other words, the capacity to handle the system - of all types. Browser.

The PC system used to test Google Chrome is the same system used for testing Internet Explorer 8 Beta 2, IE7 and Firefox.

Test results show that Chrome 'consumes' 324MB of RAM resources on a Windows XP-based PC system. Meanwhile, IE8 Beta 2 only accounts for 322MB. On average, Chrome 'consumes' 267MB of memory resources - 26% higher than the average of IE8 Beta 2.

But for Mr. Barth the test results are not surprising. Google has decided to exchange system memory resources for human safety. Each Chrome 'tab' is operated on a separate process. This is a solution that helps Chrome to quickly disable malfunctioning 'tags' or hangs without affecting other 'cards'.

' The more TABs are used, the more heavy Chrome becomes. This is a clearly defined design purpose of Google , 'Barth said.

'Heavy' Google Chrome is no less than IE8 Picture 1 . but occupy a few streams

Although 'consuming' a lot of system memory resources, Chrome is amazed at the number of processing threads that this browser occupies during operation.

' Thinking that the same direction towards next generation hardware like IE8 Beta 2, Chrome will also take advantage of the same processing power as this browser. But surprisingly, even at the peak of operation, Chrome only occupies 48 threads . '

Previous test results showed that Firefox 3.0.1 occupied 25 threads, IE7 accounted for 43 threads and IE8 Beta 2 accounted for 153 threads.

Mr. Barth highly appreciated Chrome's independent 'card' (tab) design solution to help quickly disable hanged 'cards'. ' This is a type of modular design architecture. I think Chrome only uses about 25 threads to manage the UI functions as well as the most basic ones. The number of threads exceeds when the user opens new cards '.

Chrome runs up to 12 different processes when opening 10 websites on 10 different cards. IE8 Beta 2 also has the ability to disable the hanged card, but the browser only uses about 6 different processes along with a 6-fold amount of threads compared to Chrome.

. is by architecture

' I think the very simple Chrome design has an advantage over Microsoft's IE8 .'

Although most of what has been disparaged for IE8 Beta 2 is also applied to Chrome, Mr. Barth highly appreciates the design architecture with the ability to disable the hanged 'card' that Google has Apply for this browser.

' I think this is a move to infiltrate Google's business environment. Google doesn't want all of the things users are processing on the online office suite to be completely ruined just by a TAB card that has been hung up completely . '

' I think this is something perfectly suited to exchange for memory resources that Chrome has occupied during operation. With IE8 Beta 2, Microsoft probably has the same thought . '

From this point of view, Mr. Barth criticized the design of the open source Firefox browser. ' That's yesterday's design. Firefox cannot yet be able to disable the hanged tag like today's IE or Chrome . '