Originally posted by Charlie68
View Post
Announcement
Collapse
No announcement yet.
Firefox vs. Chrome Browser Performance On Intel Ice Lake + Power/Memory Usage Tests
Collapse
X
-
I tend to disable the disk cache in Chromium browser so it doesn't hit the hard-drive constantly, but I feel that Firefox should work towards a chromium front-end with all of their security settings and make a de-googled browser with the best of everything.
Comment
-
Originally posted by nsneck View PostChrome has a better engine. Firefox is catching up, but slowly. WebRender is a good step-up, but not enough. FireFox' DOM / JS implementations are somewhat lacking still, unfortunately.
Comment
-
Originally posted by archsway View Post
My Firefox has got over 300 tabs and is using "only" 1GB.
Comment
-
Originally posted by Charlie68 View Post
If the hardware has limitations, it is a hardware problem and the differences between browsers are trivial. So better to navigate decently with one or two tabs open, than to flood the PC with 30 tabs.
Edit Otherwise, memory consumption is not a big problem on modern devices.
Most of the time, I have more than 100 tabs open.
These tests just don't cover some interesting scenarios. It's pretty obvious when you have a bit of hindsight that if you have more than 10 tabs open, Chrome becomes barely usable, while Firefox handles 100+ tabs without even wincing.
There are many reasons why my use cases and Chrome do not get along (stop videos from playing automatically and tabs below URL bar being absolute must haves), but this 10+ tabs unbearable lag of Chrome by itself is enough to get sold on Firefox.
Since Chromium only comes in flatpaks or snaps, I got rid of it and reinstalled a latest version Chrome for some Facebook-powered comments section (that uBlock on Firefox can't seem to allow even when turned off), and it's now impossible to get group tabs on Chrome without random grouping decisions, and that ugly purple colour default. That's just silly.
Comment
-
Originally posted by Mez' View PostThat's nonsense. Everyone uses its browser differently.
Most of the time, I have more than 100 tabs open.
These tests just don't cover some interesting scenarios. It's pretty obvious when you have a bit of hindsight that if you have more than 10 tabs open, Chrome becomes barely usable, while Firefox handles 100+ tabs without even wincing.
There are many reasons why my use cases and Chrome do not get along (stop videos from playing automatically and tabs below URL bar being absolute must haves), but this 10+ tabs unbearable lag of Chrome by itself is enough to get sold on Firefox.
Since Chromium only comes in flatpaks or snaps, I got rid of it and reinstalled a latest version Chrome for some Facebook-powered comments section (that uBlock on Firefox can't seem to allow even when turned off), and it's now impossible to get group tabs on Chrome without random grouping decisions, and that ugly purple colour default. That's just silly.
As you may have noticed, the behavior of applications can vary greatly, depending on the hardware, most likely on your Firefox hardware works fine, on my no.
Comment
Comment