Live data from Hacker News

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

techcrunch.com

1–10 of 346 posts

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

#4
post #3

The speed is great as long as youtube doesn't autoplay a new video which freezes the whole browser for me until it is done loading.

Whole browser freezez for me on any amazon page. Just when it starts rendering it freezes everything inside Firefox window for a few seconds. It's so annoying that I'm considering dropping Firefox after over a decade for Opera or Brave browser.

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

#6
Does anybody know more about how Mozilla manages experiments? I'd always assumed that all users downloaded an identical binary and got the same behavior. How do they assign 10% of their users to an experimental group?

Is it possible that two users will see different functionality when they are both using the same OS and release, say Firefox from the latest version of Ubuntu?

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

#7
I switched to Firefox from Chrome about 12 months ago. It isn't as good as Chrome, but I was trying to reduce my Google dependencies.

It has been mostly fine (except for an annoying OS-X multi-screen bug where it screws up the sizing).

I was really looking forward to this feature to help close the gap on Chrome performance.

Until August (I think Firefox 48.x), when it became unusable on any site with... something. I'm not entirely sure what triggers it- I don't think it is just video alone. Something make the entire browser lock up entirely for minutes, and sometimes it even runs out of memory and I have to kill it via the OS.

No add-ins (except for Firebug).

Frustratingly, I can't replicate it well enough to be a useful bug report.

I'm this close to switching back. Muscle memory and shortcuts to Firefox is the only thing stopping me.

So.. this will be great, but please make it a workable browser.

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

#8
post #4
post #3

The speed is great as long as youtube doesn't autoplay a new video which freezes the whole browser for me until it is done loading.

Whole browser freezez for me on any amazon page. Just when it starts rendering it freezes everything inside Firefox window for a few seconds. It's so annoying that I'm considering dropping Firefox after over a decade for Opera or Brave browser.

I wonder if this is the same issue as I'm seeing: https://news.ycombinator.com/item?id=12437130

Amazon works for me though. Hmmm.

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

#9
post #4
post #3

The speed is great as long as youtube doesn't autoplay a new video which freezes the whole browser for me until it is done loading.

Whole browser freezez for me on any amazon page. Just when it starts rendering it freezes everything inside Firefox window for a few seconds. It's so annoying that I'm considering dropping Firefox after over a decade for Opera or Brave browser.

Have you tried disabling the functionality in about:config?

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

#10
Its incredible multi-process took this long. Just goes to show you that your architecture decisions last a long time and are often difficult to change. Chrome had this from day one and never had a big and old codebase to worry about. Yet it took Firefox many years to get multi-process going and my understanding is that its much more limited and simpler than what Chrome or Edge do.

I'm also a little surprised there hasn't been an attempt to launch a completely new Firefox from the ground up. Regardless of what they're doing right now, its still a legacy code monster and much more laggy than the competition. Maybe this is Servo's ultimate purpose, but every Firefox advance is welcomed but always feels like another layer of lipstick on this pig.

Disclaimer: I use Firefox as my main 'non-work' browser several hours a day. Its good, but its very obvious when I'm not in Chrome from a performance/stability perspective.

Post reply on HN