
In practice , this new feature improves upon the previous “Intensive Wake Up Throttling”, introduced with version 87, which prevented JavaScript from waking up a card more than once per minute after it was suspended and hidden from view for over 5 minutes. This has led to a reduction of CPU usage up to 5 times and, consequently, to a longer battery life (up to 1.25 hours).
As explained by Google itself:
The “JS timer Intensive Wake Up Throttling” feature was released in version 86, aligning the timer Wake Ups to a one minute interval after a 5 minute period of inactivity. The 5 minute timeout is very conservative and was chosen to allow Intensive Wake Up Throttling to be launched with minimal risk of regression. We are now considering reducing the timeout to 10 seconds only for pages considered loaded when hidden.
In case you are interested in testing this new feature, you must first download Google Canary or Dev and enable it by activating the relative flag by writing “chrome: // flags / # quick-intensive-throttling-after-loading” in the address bar. The change will be complete once the browser is restarted.| ); }
Photo Credit: Bleeping Computer A few weeks ago, we told you about a particular extension for Chrome that makes the results disappear from Google. Find more details in our previous dedicated article.