There are a number of automatic exemptions from this throttling: Note that this budget regeneration rate can be tweaked as Chrome collects more data about throttling behavior.

The budget continuously regenerates with time (currently set to a rate of 0.01 seconds per second).

After a timer has executed, its run time is subtracted from the budget.

A timer task is allowed to run only when the time budget is non-negative.

A page is subjected to time budget limitations after 10 seconds in the background.

Each background tab has a time budget (in seconds) for running timers in the background.

Chrome will continue to take steps in this direction to prolong users' battery life, while still enabling all the same experiences developers can build today. In the long-term, the ideal is for background tabs to be fully suspended and instead rely on new APIs for service workers to do work in the background. We've found that this throttling mechanism leads to 25% fewer busy background tabs. Tabs playing audio or maintaining real-time connections like WebSockets or WebRTC wonвЂ™t be affected.

Via the new throttling policy, Chrome 57 will delay timers to limit average CPU load to 1% of a core if an application uses too much CPU in background. Like many browsers, Chrome has limited timers in the background to only run once per second. Starting in version 57, Chrome will throttle individual background tabs by limiting the timer fire rate for background tabs using excessive power.Д¬hrome has focused on improving the user experience by throttling tab performance for many years. This includes background tabs, which consume a third of Chrome's power usage on desktop. To prolong battery life, Chrome should minimize power impact from things users canвЂ™t see. Efficient power usage is an important aspect of speed, one of ChromeвЂ™s key pillars.

Chrome limit speed