Chromium and especially its best-known derivative, Chrome, have always drawn fame as technologies that swallow a lot of resources. This stems from the browser’s multi-threading capabilities, a feature that put it far ahead of the competition a decade (or so) ago when it came to taking advantage of the multi-core processors that had become commonplace.

However, despite the obvious improvements provided by Chromium and Chrome, Google has repeatedly given the impression that the resource consumption problem is out of control, and has more than once solved problems or improved performance by consuming more RAM.

Fortunately, Google realizes that Chromium can be a bit wild when it comes to resource consumption, so it introduced a feature called “Rapid intensive strangulation after loading“, which should reduce CPU usage by about 10% to extend autonomy laptops and mobile devices.

Earlier, Chrome 87 introduced another feature called “Intensive restriction of Javascript wake-up timer“, which prevents JavaScript from activating the tab more than once a minute after it has been suspended and after more than five minutes of inactivity beforehand. To put it more plainly and with a loss of precision, it is responsible for preventing the JavaScript code of a web page from being reactivated after the user has momentarily lost tab focus. In internal testing, Google found that Chrome’s CPU usage was reduced by five times and managed to increase battery life by up to 1.25 hours.

With the new function “Rapid intensive strangulation after loadingwhich is still in the experimental phase, Google reduced the lag time from 5 minutes to 10 seconds, causing CPU usage to drop faster and thus a further extension of the autonomy of the device.

Yes good “Rapid intensive strangulation after loading” aims to achieve Chrome in web browser format (and we bet other Chromium browsers like Edge, Brave and Vivaldi), It seems to be targeting Chrome OS, an operating system developed by Google for Chromebooks that uses the same technology base on Linux. The reason makes perfect sense if one sees that Chrome works there constantly and permanently, while on Android, Windows, Linux and MacOS it is an application that can be closed whenever the user wants.

Those interested in a feature that allows you to pause or limit the execution of JavaScript, simply download the version of Chrome corresponding to the canary or dev channel and the site chrome://flags/#quick-intensive-throttling-after-loading in the address bar to start the activation. It is expected to be at least stable in Chrome OS 105.