1

I just "upgraded" to Firefox 57, the holy grail of alleged performance perks, yada yada. Im not here to complain that it breaks all the add ons. My problem is that the response time for IO is sickeningly slow now.

In FF56, I was able to click 56 times per second, which is handy in online gaming. With FireFox 57, I am only able to register mouse clicks at about 20 times per second. This is a devastating blow to performance.

Yes, I know how to uninstall, and get firefox 56 back. What I want to know is if there is some way I can boost the click recognition ability of Firefox 57, to that which it was, (or more).

Is there a way I can allow FF57 to utilize more RAM? Or some other method for getting the same performance or better, that was present in the previous version?

OS: Ubuntu Mate 17.04

Improve this question
3
  • 4
    56 clicks per second? Wow, how do you avoid the overheating of your mouse? :-) Commented Nov 17, 2017 at 3:54
  • It gets warm, but doesn't over heat. For now, I will be using Firefox56. Until a solution presents itself, or I figure something out. A tip to get fast response time out of any browser: zooming out to 30% helps a lot. at 100% screen size, I get mad lag, before getting to the 60s range of Cps. Commented Nov 18, 2017 at 22:18
  • I am not sure that my answer will actually help, if it doesn't, I am ready to delete it. Commented Nov 19, 2017 at 11:57

1 Answer 1

Reset to default
0

Firefox has a new development, so-named electrolysis. Its essence is that they gave up to build a multithreaded browser, and they switched to a mixed, multithreaded-multiprocess model.

The result is suboptimal memory consumption, zombie child processes and decreased speed.

Google chrome does the same, but they have much more programmers to make it better.

Fortunately, e10s can be turned off. Essentially, you have to search for "remote" in the about:config and switch every "true" boolean value to "false".

Improve this answer
9
  • I'm confused. "suboptimal memory consumption, zombie child processes and decreased speed." This is supposed to be an improvement? Commented Dec 11, 2017 at 10:32
  • @FaheemMitha No, it is not an improvement, it is a conceptionally false direction, in my opinion. Commented Dec 11, 2017 at 10:33
  • Oh. Do you recommend I stay with 52 ESR on stable then? Commented Dec 11, 2017 at 10:37
  • @FaheemMitha I recommend to turn off the e10s. Furthermore, using 32-bit FF can also help a lot. Sad to say, but so is it. I was militant "do everything with 64-bit" long, but slowly the facts convinced me. The major reason, why the 32-bit ff still better is, the cpu cache. Commented Dec 11, 2017 at 10:42
  • I don't know what e10s. And why should I use 32 bit Firefox on a 64 bit system? Should we take this to chat? I'm in the main chat room - chat.stackexchange.com/rooms/26/dev-chat Commented Dec 11, 2017 at 10:55

You must log in to answer this question.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.