Zlip792 wrote:Another snappy down, first shutdown improvement which as per Talos result improved shutdown great deal. Second snappy is Session file should be read on background thread landed on Inbound.
Bug numbers please? *EDIT* Oh.. shutdown bug affects only Linux
Zlip792 wrote:Another snappy down, first shutdown improvement which as per Talos result improved shutdown great deal. Second snappy is Session file should be read on background thread landed on Inbound.
Bug numbers please? *EDIT* Oh.. shutdown bug affects only Linux
Nope, I don't think it was CC related something so it will affect all OS. Let me confirm.
Zlip792 wrote:Another snappy down, first shutdown improvement which as per Talos result improved shutdown great deal. Second snappy is Session file should be read on background thread landed on Inbound.
Bug numbers please? *EDIT* Oh.. shutdown bug affects only Linux
Looks like there are lots of OMTx ( Off Main Thread ) update in the Nightly Channel. I am on Aurora Channel so i will have to wait to feel if improvement went through to UX.
Just so I'm understanding this correctly, Firefox is currently multi-threaded but not multi-process correct? With OMTC, it will separate the UI into one process, and everything else into another? How will we know when this is enabled? With there be 2 processes showing up in task manager, Firefox and FirefoxUI or something similar? Also, will this do anything to fix the problem of Firefox only being able to use 1 core of a cpu, or is that another problem entirely? I have a dual core AMD and task manager only shows cpu using 50% even when it is obviously maxed out.
Nonetheless, I'm really hoping OMTC will improve responsiveness of the browser, it's the only thing that bothers me compared to Chrome.
Even SuperSnappy will still be one process IIRC. Right now the UI and content run off the same thread - with the exceptions of IO, IonMonkey compilation, web workers etc. The list is growing but only SuperSnappy or something similar can complete it.
Ver Greeneyes wrote:Even SuperSnappy will still be one process IIRC. Right now the UI and content run off the same thread - with the exceptions of IO, IonMonkey compilation, web workers etc. The list is growing but only SuperSnappy or something similar can complete it.
True, though the work needed to break UI and content into separate threads should get us relatively close to being able to split them to separate processes.
mozillaZine is an independent Mozilla community and advocacy site. We're not affiliated or endorsed by the Mozilla Corporation but we love them just the same.