4 ms·
I wish this could be (maybe it already can be?) disabled for environments where I don't care about battery life/power consumption. This change probably saves me
by vdnkh 10y ago
I wish this could be (maybe it already can be?) disabled for environments where I don't care about battery life/power consumption. This change probably saves me a fraction of a cent per month at the cost of a worse web experience (I'm a bit of a tab hoarder).
- gnicholas 10y agoGood point, although I find that performance is always an issue—even when I'm plugged in. I'm also a tab hoarder (though more in Firefox, thanks to Tree Style Tabs), and I find that my Mac's sluggishness is always caused by having too many tabs open. Sadly, my workaround has been to quit and re-launch browsers, which presumably has a similar effect to this update. Looking forward to seeing if the new version keeps things snappier...
- erikdesjardins 10y agoSeems that it can be turned off at: chrome://flags/#expensive-background-timer-throttling ...though they may eventually remove the flag.
- joshstrange 10y agoGood for debugging an issue for sure but if you do any web-dev I'd shy away from disabling it for fear you might miss something that breaks on one of your sites because of it.