3 ms·
My Firefox setup blocks JavaScript by default. It has been peachy with NoScript and a bunch of other addons since forever. After Firefox switched to the new "Qu
by rhn_mk1 6y ago
My Firefox setup blocks JavaScript by default. It has been peachy with NoScript and a bunch of other addons since forever. After Firefox switched to the new "Quantum" verion, my extensions got reshuffled and I'm using uMatrix to block scripts.
However, even with scripts blocked, Firefox eats up a whole lot of CPU power, even on static, unchanging pages. What was <1% is now 5% CPU.
Given the Quantum promise of a speedup, I'm rather underwelmed.
- freedomben 6y agoI use both chrome and Firefox all the time to separate work and personal, plus dev testing (yes I have a lot of RAM :-D It seems to be that Firefox uses more cpu and better on memory, whereas chrome is the opposite (although by by means is chrome "light" on cpu).
- paulryanrogers 6y agoMy experience with Firefox quantum was the opposite. Ff became immediately faster and more useable. Experience seems to vary by hardware, sites, and add-ons.
- NikolaeVarius 6y agoI have 8 tabs open including a youtube tab, and FF is taking 0.5% CPU. Quantum was a "quantum" leap faster than what FF had become.
- cheph 6y agoI don't use it that often, but last I tried switching to it this was also one of my biggest problems, it was simply using too much resources when it was literally doing nothing, where chrome, doing much more, used much less CPU power. I don't like chrome, firefox is feature wise better IMO, but I am not patient enough for it. Maybe it is just my setup, and the plural of anecdote is not data, so my experience may be an outlier, but I wish it was not my experience.