Google management chrome

Google also say they’re using a “multi-process design” which they say means “a bit more memory up front” but over time also “less memory bloat.” When web pages or plug-ins do use a lot of memory, you can spot them in Chrome’s task manager, “placing blame where blame belongs.”
If this is true, case management, you see how many resources are consumed in a given browser, labels (including plug-ins!) This is a killer feature 100% of the browser.

She would not have been able to implement the current structure of the browser, which does two things: 1) no problem with the browser, because a lot of rewriting code that will lead to and 2) there is a general agreement that this structure will actually consume more resources than the current structure.

This is very important. In the absence of the need to share transmission between the browser, you can not simply reduce the amount of resources has doubled. For example, in Mozilla's Gecko engine, a large number of reusable code took place, significantly lower memory consumption (and optimize the memory of collecting and sorting garbage).

But the friction here.

The poor performance or failure of memory consumption is no longer a browser, but the Web site.

In implementing the features of the browser is an entirely from memory, or transfer of all criticism of the performance of individual site owners ( "wow, my browser is the use of 300MB of memory! Actually, it is only 290MB of all consumers youtube.com, they should develop their own web pages! "). This will be a major change of responsibility for network development - one of the best website in its entirety.

Naturally, there is indirectly linked to the main browser - but maybe it will be marginalized.

This is an incredible loss (in the best sense), it is a strategy, browser vendors will be forced to react. How will the response occur is another matter entirely.

Once, but two things happened: The browser will start competition, reduce specific memory / performance figures for specific Web site (the current situation - but with the number of users will do well to ask for it) and the browser will attract Located .

Since the browser is the Herald of a new de facto "specific" (he is no longer a window in process management, for example), they must take every opportunity to exaggerate the number of those who own interests.

In many levels, the new feature will change the structure of the browser and how it communicates the user. While the introduction of chromium Google is not just belong to the end of the runway in the fierce blast, the user will be curious, as well as wounds seeds: the browser must find a way to respond.



This is a very small (and apparently very bad), but he seems to be on the details of the three attributes of each label: CPU usage, memory utilization and network.

It will be exciting to see what kind of user-centric user interface to solve the problem. Guide to the use of a large number of CPUs in the red? Consumes a large amount of memory, the more? It seems that there are many ways, the quality of the guidelines as may be appropriate