Linked by David Adams on Wed 3rd Aug 2011 16:50 UTC, submitted by _xmv
Thread beginning with comment 483593
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[2]: Not a very good test
by renox on Thu 4th Aug 2011 12:26
in reply to "RE: Not a very good test"
I cringe every time process separation is mentioned as a mean of resource management.
Oh really? So explain to me: how do you know which tab use 99% of CPU/too much memory in Firefox?
With Chrome it's easy: it has an integrated "task" manager.
Look: the default "share nothing" of processes is much better from a security, resource management POV than "share everything" of threads: threads are an optimisation, that's all.
RE[3]: Not a very good test
by jacquouille on Thu 4th Aug 2011 13:48
in reply to "RE[2]: Not a very good test"
"I cringe every time process separation is mentioned as a mean of resource management.
Oh really? So explain to me: how do you know which tab use 99% of CPU/too much memory in Firefox?
With Chrome it's easy: it has an integrated "task" manager. "
In Nightly (Firefox 8), in about:memory you can see how much memory each tab uses. In general it's true that multiple processes make it easier for the user to know which tab is using what.
Look: the default "share nothing" of processes is much better from a security, resource management POV than "share everything" of threads: threads are an optimisation, that's all.
Firefox is eventually moving to a multi-process architecture a la Chrome (though that's probably still 6 months away). So for sure Mozilla agrees that's the better approach. But notice that not even Chrome can rely on that for security, since above a certain number of open tabs, multiple tabs end up sharing the same process. I also wouldn't say that "threads are an optimization, that's all". Threads are light-weight processes, i.e. processes that share the same address space.
Edited 2011-08-04 13:48 UTC





Member since:
2007-06-22
I cringe every time process separation is mentioned as a mean of resource management. It actually is only useful to hide inefficiencies by hoping that the process will be shut down before its resource usage causes noticeable problems. I'd rather have the browser developers discover and fix memory leaks and optimize their data structures before relying on such heavy-handed "solutions".