Chrome has been labeled a resource guzzler for years, read memory, but also autonomyand Google has been working for years to solve it, or rather to mitigate browser gluttony, given that performance requires resources. That’s why there have been patches one after the other for years.

Interestingly, six years ago Google countered Microsoft’s accusations – the Redmonds didn’t know they were going to eat it with potatoes – and ensured that Chrome (53) no longer eats batteries, although the truth is that these types of complaints happened before and after, especially in relation to the impact that the browser has on the autonomy of the portable device.

In this regard, Google continued to implement measures improve Chrome performance and consumptionfor example, by tweaking certain settings one way or another, usually through the processes of exhaustively checking the resource usage (CPU and RAM) of Chrome itself.

As a user-friendly feature, freezing cards that aren’t being used to free up memory as part of the “battery saver” mode will sound familiar. But there is also a “high efficiency” mode. What’s unique about both modes is that they’re alien to the user: it’s a browser that manages itself… and that’s not always right. So Google intends to solve it with user intervention.

To this end, Chrome developers are working on two indicators that the user can activate and deactivate on demand, forgive the redundancy, turn battery saver and high efficiency modes on and off. As simple as a click and… done!

As far as is known, battery saver mode (the lightning bolt icon) will de facto work with certain background processes, in addition to reducing Chrome’s visual effects and thus power consumption. On the other hand, high efficiency mode will do the same with background tabs, be able to specify a time or add exceptions for websites.

Of course, neither is available to regular Chrome users at the moment, as these are features that are still under development and will take more or less time to be implemented…only in Chrome, or will they also be implemented?in other Chromium derivatives ? We’ll have to see, but in principle it shouldn’t be a problem to make it a shared feature.

BTW: This was discovered by the same Reddit user who alerted us to the image editing feature in Microsoft Edge or the note taking feature in Chrome, neither of which have yet made it to the stable version of their respective browser. But everything will be fine.