Hacker News Reader

Comment by TazeTSchnitzel | Hacker News Reader

The problem with e10s (Electrolysis, codename for multiprocess Firefox) is it's actually less concurrent and runs far worse than normal Firefox, at least currently. It's downright unusable.

View on HN

Switching tabs is just awful. If one page is busy loading something, I want to switch to another tab and see what's there, but instead I get to stare at the word "Connecting..." for several seconds. I just feel like I'm waiting for the browser to catch up all the time.

FYI, you can help submit a performance profile to Mozilla so they can work to resolve this: http://mikeconley.ca/blog/2015/05/04/electrolysis-and-the-bi...

Thanks for the link. It's almost certainly one of my addons that's causing the trouble, but I like my addons!

This is the exact opposite of my experience with current nightly. The browser feels very snappy and I have yet to see memory usage climb above ~350 MB with a multitude of JavaScript heavy tabs open. (Although I don't know if e10s is directly responsible for the latter.)

It may have less performance for various reasons, but it can't be less concurrent by definition. Previously there was no concurrency.

You can have concurrency with only one thread. What you cannot have is parallelism.

More context here: http://stackoverflow.com/questions/1050222/concurrency-vs-pa...

Yes, and I believe that before the layout didn't happen concurrently with other stuff in the browser. It was called on a change and the rest of processing waited. Is that not right?

Reply on news.ycombinator.com