3 ms·
I've noticed on MacOS (on two MBPs) that Firefox 69 (with ublock origin as only plugin) is noticeably slower to render / lay out sites and maybe download conten
by berkut 7y ago
I've noticed on MacOS (on two MBPs) that Firefox 69 (with ublock origin as only plugin) is noticeably slower to render / lay out sites and maybe download content than Chrome (with ublock origin as only plugin) on same machines. Battery life is noticeably worse as well compared to Chrome.
I've switched though to using Firefox despite the above on MacOS at least.
On Linux however, Firefox seems quite a bit worse than Firefox to the extent that it's approaching "painful" levels to use it - scrolling is very laggy (messed around with hardware accel, drivers, etc), downloading / rendering is noticeably slower, etc. (Same setup of only plugin in each browser on Linux being ublock origin). Even starting it seems much slower (with cold FS caches).
This is on several Linux machines, and seems pretty universal in my experience.
At work, we have to use the internet through a VDI terminal (main network is completely segregated from internet), and I've noticed that with this setup, Firefox is even slower than my "native" Linux comparisons. Also, as I can see the network traffic between the VDI and my machine, I've also noticed that a single blank page window in Firefox keeps sending updates (300KB/sec, like it's refreshing constantly in an event loop or something), whilst a blank page window in Chrome has no updates, which seems a bit weird to me, and indicates something's non-optimal in Firefox, as I don't see why a blank page should cause firefox to apparently re-render stuff...