In an attempt to improve Google Chrome’s performance and reduce its impact on battery life, Google is testing two new features for the browser. The first feature, which was spotted in a Chromium bug tracker page, adds a new battery-savings meta tag that will optimize websites that are known to have high CPU or battery costs. An explainer regarding the new meta tag states:-
“Saving battery or CPU is important for computing devices that are not connected to an electrical source, or to better share common CPU & GPU resources among running processes…Web sites that are known to have high CPU or battery costs may want to request that the UA optimize for CPU or battery, even if the users has not requested it…Most modern OSes also have battery saving features that kick in either when the battery is low or the user wishes to save battery. Ideally web sites should be able to respect these settings. Sites may wish to advice the UA on which strategies work best for the side in these situations.”
The explainer further highlights that the battery savings feature will have the following components:
* A meta tag that allows sites to indicate preferred modes.
* Media queries allowing sites to adjust their style sheets according to battery savings.
* Spec text saying that if the user or OS has gone into a battery savings mode, then the User Agent should apply one or more of the battery savings to the sites.
* Spec text saying that UAs should respect the meta tag on a site unless it conflicts with user or OS settings.
The second feature, which aims to improve Google Chrome’s performance, is restricted to Android devices. The feature has been added to the browser under a new flag called cpu-affinity-restrict-to-little-cores, and its description reads as follows: “Restricts Chrome threads to LITTLE cores on devices with big.LITTLE or similar CPU architectures.”
As per a recent report from Chrome Story, the feature is expected to make Chrome more power-efficient on ARM devices and improve its performance. The feature is currently in the experimental stage, and Google is studying its impact on power consumption, smoothness, and other system health metrics. Therefore, we may have to wait quite a while before the feature makes its way to the stable version of the browser.