You have to recognize the good and the bad: today, Google Chrome is one of the most “greedy” applications when it comes to resource consumption, but it is also true that multiple circumstances concur in this problem: from web pages that, either due to the complexity of what they offer or due to the poor optimization of their code, suppose a huge workload, to that common habit of opening tabs and more tabs until being unable to read the description of each one of them (he who is free from sin, let him cast the first stone).
And it is also undeniable that those responsible for the Google browser are constantly working on the search for solutions that help reduce the impact that Google Chrome has on the resources of the systems in which it is used. For example, with the arrival of Windows 10 2004 (May Update) and, with its help, improvements in memory management, we learned that they began to work to use SegmentHeap to replace LegacyHeap, a much more efficient management method for managing memory mounds and memory provisioning. Unfortunately, yes, at least for the moment we cannot count on it.
And when we are still waiting for the final arrival of this optimization, as well as for the engineers to find the right way to implement SegmentHeap, we know from The WindowsClub than They are working on another new Google Chrome feature to reduce battery consumption and, it is to be expected, also of the rest of the resources of the systems in which it is used. And the most surprising thing is that it will not only depend on the browser itself, no, web pages will also be participants in the process.
And what does this new feature consist of? Well, in defining a new meta tag, in which the website itself is the one that, knowing how it works and what processes within them can be especially voracious, will use that tag to inform Google Chrome about what adjustments can be made (reduce script execution frequency, video frame rate, visual effects, etc.) when necessary. In this way, if the user of the system selects a low battery consumption mode, the browser will recognize it and will be able to make the settings specified by the website itself.
This advance of Google Chrome makes a lot of sense if we talk about complex web pages, but it goes even further in a scenario in which progressive web applications are growing gradually. Once the browser becomes the interface and the resource manager of applications with which we can work on a daily basis, it makes all the sense in the world that browser and websites work hand in hand to be more efficient in all aspects, also in the consumption of resources.
Leave a Reply