Re:Firefox fixes save gigabytes of memory on image-heavy pages
by sliverstorm on Tuesday October 01, 2013 @02:18PM
(#6478040)
Maybe multi-process is the reason... I've recently started using Chrome more on my sub-notebook because Firefox gets really choppy even though it has lower memory usage. Perhaps the explanation is Chrome can be scheduled to all four of my 1GHz CPU cores, as compared to Firefox which will be on just one?
[ Parent
| on HN ]
Re:Firefox fixes save gigabytes of memory on image-heavy pages
by option_greek on Wednesday October 02, 2013 @03:48AM
(#6481218)
Nope. Threads can use multiple cores as well. No need to launch separate process for it.
Re:Firefox fixes save gigabytes of memory on image-heavy pages
by sliverstorm on Wednesday October 02, 2013 @04:25AM
(#6481303)
Ah yes, of course. I should have remembered that. So Firefox is multi-threaded now?
Re:Firefox fixes save gigabytes of memory on image-heavy pages
by option_greek on Wednesday October 02, 2013 @07:10AM
(#6481747)
As far as I know, it has always been. Unlike javascript which usually runs in a single thread, the browser itself is free to use as many background threads as it wants to load resources, render graphics etc. Only javascript is usually run as single thread per tab (unless the webpage uses web workers).