Regarding Chrome’s Power Efficiency on OS X

Vlad Savov, writing for The Verge:

While reviewing the new MacBook Pro with Retina display, I ran the usual Verge battery test on Apple’s new machine. With the screen set to 65 percent brightness, it cycles through a series of websites until the laptop’s battery gives out. The native Safari made the new Retina machine look good: 13 hours and 18 minutes. Google’s Chrome, on the other hand, forced the laptop to tap out at 9 hours and 45 minutes.


Apple and Google must both bear a portion of the blame for this ongoing calamity. The MacBook maker has a vested interest in promoting Safari as the most efficient, fluid, and pleasing web experience on its platform. Safari will always have the advantage of being optimized for the latest OS X release ahead of any other browser, which means its lead in efficiency will never be completely eradicated. But three and a half hours? That’s the sort of gap that Google should be able to close — if it makes optimization its priority.

I don’t see how this is Apple’s fault or responsibility in the least regard. Are there accusations that Safari is using private APIs unavailable to Chrome that allow for this efficiency? It seems to me like the usual result of a cross-platform app (Chrome) vs. a platform-optimized one (Safari).

Update: Many readers have emailed to suggest that Chrome’s energy consumption problems might be due to its built-in support for Flash Player. I’m sure that doesn’t help, but it’s almost certainly not the only difference between Chrome and Safari. Comparing Chrome to Safari in Activity Monitor’s “Energy” tab is a real eye-opener.

Saturday, 18 April 2015