[FreezerburnV]

I guess I could give it a try. I see this kind of thing across both macOS and Windows though, but I do have sync on so theoretically there could be something there causing extreme issues across multiple computers and 2 OSes, generally despite me trying to even follow stuff like FasterFox to make it work better.

[pcwalton]

Don't use Fasterfox. It tweaks many settings that frequently result in performance regressions. The default networking-related settings are set the way they are for a reason.

[FreezerburnV]

Performance has not been a complaint of mine, especially network-related. It's everything else. Almost like Firefox is optimizing for just shoveling as much CPU power and RAM as possible into it's gaping, bloated maw, not caring about anything else. Kinda like an old mail application from a startup I worked at. Nothing has ever matched how amazingly good it was at certain things it did (or even have similar features), but hot DANG did it just drink battery like its going out of style.

[pcwalton]

> Almost like Firefox is optimizing for just shoveling as much CPU power and RAM as possible into it's gaping, bloated maw, not caring about anything else.

That is of course not the case.

[PrimeMcFly]

Use a fork like Librewolf, and look into having a customized user.js for performance tweaks. There is a lot you can do.

For me, currently, my setup is the best browser I've ever used.

[pcwalton]

Don't use a fork and don't customize your user.js. It is exceedingly unlikely that excess power consumption is caused by anything you can easily tweak. Instead report issues to Mozilla.

[PrimeMcFly]

Very bad advice.

Some forks have clear advantages, are well maintained and trustworthy.

There are numerous reasons to maintain a user.js file also, not just performance reasons.

Indeed, report issues to Mozilla directly, but that isn't inconsistent with using a fork and maintaining a user.js