4 ms·
Test: open 10 tabs of techmeme.com, on OSX Catalina (10.15 Beta), on a 2015 retina 13" macbook pro. Firefox: Threads 71, %CPU 2.5. Energy: 0.4. Opening the tab
by munmaek 7y ago
Test: open 10 tabs of techmeme.com, on OSX Catalina (10.15 Beta), on a 2015 retina 13" macbook pro.
Firefox: Threads 71, %CPU 2.5. Energy: 0.4. Opening the tabs all at once took up ~68% CPU. Energy went up to 75.
Safari: threads: 8, %CPU: 0.7-2. When opening the tabs: %CPU: 28%. Energy usage: 2.4.
Firefox grew sluggish when opening that many tabs at once. Safari handled it like a champ.
Pretty bleak for firefox.
- billiam 7y agoMozilla's priorities are (and have mostly always been) for FF on Windows. It's a gripe that me (and the great majority of FF devs who use Macs and Linux boxes) have been suffering under for years) that those OSs will just never be the highest priority--and the reasons why have much to do with Apple and their Apple-first mentality for their platform. It is only partly a joke that the last users of Firefox will be software developers and their grandmothers. But there are a lot more grannies than devs.
- daemin 7y agoAs other people have mentioned, Safari doesn't load/run tabs in the background. What happens when you switch to each of those tabs so you can use the site?