logoalt Hacker News

wilkystylelast Tuesday at 4:51 PM2 repliesview on HN

I suspect that the people making these claims that Safari is no longer the most battery efficient are not Apple users. It's quite easy to empirically validate which browsers are most efficient by looking at the average energy impact in Activity Monitor. Safari is the winner, Chrome/Brave are not far behind, and Firefox is the clear loser.


Replies

kseclast Tuesday at 5:06 PM

I use all three.

Safari loses out when you run with a lot of Tabs. Both Chrome and Firefox knows when to unload tabs. ( Firefox even have about:unloads to tell you the order of Tabs it will unload! )

Try opening Tab Overview in Safari and it will start loading all the website for thumbnails, paging out to disk due to low memory, writing hundreds of GB to page. It also put Tabs on low running priority in the background rather than pausing them like Firefox or Chrome. ( Not sure if that is still the case with Safari 26, at least it was with 18 ). To combat that, restarting the browser time to time helps.

Safari is well tuned for iOS as a single tab, single page usage. On MacOS when doing many tabs it start to get slow and inefficient. And this is very much a Safari issue not an Webkit issue because Orion is a lot better at it.

And yes I have filed Radar report for many of the issues but I have come to the conclusion Apple doesn't care about multi tab usage on desktop Safari.

phantasmishlast Tuesday at 5:06 PM

I think the difference is fundamental to the engine and the gap will be hard to close, too (I mean, how long has it been and the gap remains?). WebKit-based ultralight browsers remain usable after you’ve cranked hardware specs down far enough that nothing based on Chrome or Firefox’s engines do. Resource use among the three engines seems to differ at some kind of low, basic architecture level.