One of the worst deficiencies in today’s browsers is the single thread per tab and one process per browser module. Opera, Firefox and IE would continually grow in memory. Memory allocated for new tabs are never deallocated and recycle, even if you close that tab.
A simple experiment with an IE instance and 50 tabs would show the defficiencies in that single process model. 
Once a single tab crashes, the entire process would fail; therefore, You would lose all your tabs and your work in progress. If check process explorer while running Google Chrome, you would find multiple chrome.exe instances. It is a different design, chrome uses a multi-processes design, in addition to multi threading. Every new tab in the browser is a new process with its own memory space, this is significantly different and it enhances the way of browsing and multi tasking within a browser. also If one site/tab crashes, the browsing issue is mitigated. And that single tab/process would be closed. All of it’s memory would be freed, and other tabs are saved. The main browser window has its own task manager, and could be used to close independent tabs/web applications
Once a single tab crashes, the entire process would fail; therefore, You would lose all your tabs and your work in progress. If check process explorer while running Google Chrome, you would find multiple chrome.exe instances. It is a different design, chrome uses a multi-processes design, in addition to multi threading. Every new tab in the browser is a new process with its own memory space, this is significantly different and it enhances the way of browsing and multi tasking within a browser. also If one site/tab crashes, the browsing issue is mitigated. And that single tab/process would be closed. All of it’s memory would be freed, and other tabs are saved. The main browser window has its own task manager, and could be used to close independent tabs/web applicationsOne of my friends has noticed increased performance of Ajax controls when running the site (SharePoint site) in Chrome, the reason for that is that Chrome is using V8 JavaScript Engine which COMPILES JavaScript to machine code that runs within the process instead of using Javascript as a script language and interpreting it, thus any JavaScript will run so much faster.
Conclusion: I believe their browser will grow very quickly in the market since they are considering Web2.0 and Web Applications into the design and architecture form the beginning, they are also performing Quality Control Tests using their Google Database of top ranked sites, can you top that with a better diverse list of test cases, I just hope it complies with CSS standards but at the same time be intelligent enough to render IE custom styles correctly as well, I also hope that they will not create their own standards and force us developers to start customizing Google Chrome hacks for it as well with their market share.
No comments :
Post a Comment