Live data from Hacker News

Multi-process Firefox brings 400-700% improvement in responsiveness

techcrunch.com

221–230 of 346 posts

Re: Multi-process Firefox brings 400-700% improvement in responsiveness

#221

Earlier quoted context omitted.

Except mobile hardware which does not. Power usage is always a concern.

Power usage has little to do with memory usage. In fact, if the browser is using more RAM as a cache, it won't hit persistent storage as much, which actually increases battery life.

If that exaggerated RAM use causes other more intensive apps and their data to be evicted, that can cause a much more significant load when the app has to spin up again and re-acquire or re-calculate its state.

Re: Multi-process Firefox brings 400-700% improvement in responsiveness

#222
post #210

Earlier quoted context omitted.

Maybe I'm misreading things but it looks like it's been constantly getting worse since 2012?

You are misreading given that there were big improvements in memory measurment and some of the memory use increase you notice are just firefox measuring better it's own memory

Where are those improvements reflected in the graph?

Re: Multi-process Firefox brings 400-700% improvement in responsiveness

#223

Earlier quoted context omitted.

> I'm also a little surprised there hasn't been an attempt to launch a completely new Firefox from the ground up. Check out Servo: https://servo.org/

As a fully rewritten browser engine, how will they handle malformed HTML? Will it, like other browsers, try to 'understand' and fix some errors or will it stick to the specification?

The HTML5 specification now fully specifies what to do in the face of malformed input. That's one of the biggest differences between HTML5 and previous specifications.

Re: Multi-process Firefox brings 400-700% improvement in responsiveness

#224

I've got 732 tabs open at the moment and performance is still fine. The upper limit for my machine seems to be about 745 ish - much beyond that and FF runs out of video memory or something (new tabs render sites half black).

You need to get a better handle on your life.

Some bugs might only occur on extreme conditions.

Re: Multi-process Firefox brings 400-700% improvement in responsiveness

#225

Earlier quoted context omitted.

Have you given the built-in Firefox dev tools a try? If so, what did you feel was missing?

Really just that I've used Firebug for so long that using anything else is painful . I've tried switching but always ended up going back. Much of it is interface differences, but some of it is actual differences in functionality: if Firebug has something which another inspector does not, then it's super-frustrating. If another inspector has something that Firebug lacks, then I don't even notice. Edit: I should emphas…

PSA: The Firebug you know (version 2) is incompatible to e10s and there will be no e10s-compatible Firebug 3. Instead, Firebug.next is built-into Firefox(!):

https://blog.getfirebug.com/2016/06/07/unifying-firebug-fire...

Re: Multi-process Firefox brings 400-700% improvement in responsiveness

#226
post #23
post #19

“We can learn from the competition,” said Dotzler. “The way they implemented multi-process is RAM-intensive, it can get out of hand. We are learning from them and building an architecture that doesn’t eat all your RAM.” That's the money quote here. I've been waiting for this for a long time actually. Every browser I've tried except Firefox just basically eats all my RAM and other app performance (e.g. compiling stuff…

A few years ago if you'd told me FF would be the RAM-sensitive browser, I'd have laughed you off the internet.

honestly its been years now that FF is one of - if not the - browser which uses the least amount of RAM.

Its also one of the most energy efficient on most platforms.. (edge is more efficient on Windows, though it does not take into account that the engine is always running even if another browser is in use)

Re: Multi-process Firefox brings 400-700% improvement in responsiveness

#227

Earlier quoted context omitted.

And they're still at it, too: https://areweslimyet.com/

Maybe I'm misreading things but it looks like it's been constantly getting worse since 2012?

it makes sense though as more features are in use on the set of tested pages, these will inevitably use more ram.

its good to monitor and ensure that stays within acceptable parameters though, and potentially improved upon again. at least the gain is pretty slow since they "fixed all the stuff"

Re: Multi-process Firefox brings 400-700% improvement in responsiveness

#228
post #43
post #28

Earlier quoted context omitted.

Can someone describe what the "architecture that doesn't eat all your RAM" here is? Is it possible that it will inadvertently provide weaker security protections between tabs than the more naive and RAM-intensive architecture?

a) your security should not rely on process isolation. the javascript engine etc. should be secure in the first place. if you can break out of the JS sandbox you can already attack addon scripts (think password managers) b) hosting some tabs in the same, sandboxed process is still stronger than hosting all of them in the parent process.

security is multi-layers. You should not rely on either process isolation (ie process sandbox) or logical sandbox or fault-free code...

that said i think firefox's choice is more sensible.

Re: Multi-process Firefox brings 400-700% improvement in responsiveness

#229
Ive been testing Firefox e10s as in multiprocess Firefox for months now (in Nightly, and even before that).

At some point it became very usable and it still is today. HOWEVER while the interface is, yes, much more responsive, it is also NOTICEABLY slower.

I ended up reverting recently and I'm using single process Firefox right now. Its fast even thus from time to time the UI may block if there's heavy stuff going on.

Whatever makes e10s slow they gotta fix it... I suspect there's a lot of synchronization code.

Re: Multi-process Firefox brings 400-700% improvement in responsiveness

#230
post #226
post #23

Earlier quoted context omitted.

A few years ago if you'd told me FF would be the RAM-sensitive browser, I'd have laughed you off the internet.

honestly its been years now that FF is one of - if not the - browser which uses the least amount of RAM. Its also one of the most energy efficient on most platforms.. (edge is more efficient on Windows, though it does not take into account that the engine is always running even if another browser is in use)

I can second the energy efficient thing, at least in Linux.

I've been tracking lots of programs with powertop, including many browsers, in the quest of an efficient desktop and Firefox is pretty good.

I also appreciate its great plugins. With vimperator I can configure Firefox using a dotfile, and setup lots of neat things like:

1. A ssh proxy mode that also routes DNS queries

set! network.proxy.socks=localhost

set! network.proxy.socks_port=8888

set! network.proxy.socks_remote_dns=true

command -nargs=1 proxy set! network.proxy.type=

2. Site-specific Google searches, with autocomplete for the site URL

command -nargs=+ -complete=url site open google site:

map s :site

All this is really neat functionality, and very simple to achieve. I am waiting for good per-tab sandboxing, but in the meanwhile I have aliased firefox to /usr/bin/firejail so the whole application is sandboxed.

Apologies for the offtopic, but it's really exciting how a program that seemed to have lost development momentum is becoming really great again. Quite close to being the emacs of browsers if you ask me, with so many features and scriptability. Paradoxically you can get best access to these features with a plugin that tries to emulate vi, but you get the idea!

Post reply on HN