With an actual foreground task going on, the difference was less dramatic but still significant: without throttling tabs, Chrome lasted 4.7 hours, and with throttling, it got an extra 39 minutes, lasting 5.3 hours. It swapped out the blank foreground tab for a YouTube video. The first test showed just how much power can be sucked up by background tabs, but the next test was more of a real-world use case. Normally, background tabs can trigger a wake-up once per second. Now, in Canary, if you turn on the "Throttle Javascript timers" setting, any tab that has been in the background for more than five minutes will have these timers disabled, with wake-ups limited to once per minute. When you have a bunch of tabs open, these timers can chew through a good amount of battery for no reason. This also happens on background tabs, which really isn't useful since, by definition, a background tab isn't being interacted with. JavaScript timers often track user interaction with a webpage, checking things like the scroll position and ad interaction while a tab is open. As spotted by TheWindowsClub, a new flag in the Canary version of Chrome called "Throttle Javascript timers in background" will cut down on the processing that normally happens in background tabs, and it could add two hours to a laptop's runtime. The latest experimental addition to the Chrome browser promises to save a ton of power usage.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |