Chrome 57 introduces a news CPU throttling feature for the purpose of reducing desktop power consumption.
Chrome has long been reputable for optimized rendering performance and perfect plugin system , no matter when it is running on Mac or PC. But at the same time, many laptop users are criticizing it for memory leaks and high power consumption. The newly launched Chrome 57 is regarded as an another effort to solve the problems.
Making the fastest browser has always been the key pillar of Chrome. But the truth is, no efficient power usage, no speedy Chrome. In order to prolong the battery life, Google decides to throttle unnecessary power consumption for background tabs of Chrome 57. According to the search giant, a third of Chrome’s power usage on desktop is consumed by the background tabs. Throttling individual background tabs via setting limitation to the timer fire rate for excessive power used by background tabs can help dramatically reduce the overall power consumption.
Starting with Chrome 57, the Page visibility API can be used for the detection of opening pages in the background and suspension of all unnecessary work, for instance, visual updates. It is estimated that nearly 75 percent of CPU usage will be saved due to the simple optimization.
Shipping in Chrome 57, there is a budget-based timer throttling, which is an extension of the timer alignment mechanism attached to Chrome 11. The updated background timer throttling sets time limitation on running timers in the background. Assume you have opened 10 pages, Chrome 57, after the 10-second period, automatically limits the average CPU load to 1% of a core for the all pages except the one you are scanning.
The new feature is not valid for all types of web pages since different type of web pages come with different function and purpose. A tab that is playing audio or maintaining real-time connections will not be affected by the budget-based timer throttling. And if a web developer introduces a corresponding CPU during the development process, he can help save power usage for the tab as well.
In addition to the new Chrome 57 Throttling Mechanism reducing 25 percent busy background tabs, Google is in hope of fully suspending the background tabs automatically rather than relying on APIs for service workers to do the job in the background.
It is also reported that Google’s next big effort is likely to save the memory on the RAM. Just as we mentioned above, besides high power consumption, the Google Chrome web browser has also been complained about consuming too much memory. The tech giant has explored multiple ways to improve the situation and make the browser as light weight as possible. Apparently, it has not yet found the perfect solution. Maybe we can hold an expectation for its Chrome 58 version.