Re: [e10s] Higher priority handling for vsync in child processes
vsync handling happens usually right after a task (per HTML spec). Basically we have now two event queues with similar priority, and they are handled the same priority, but since the other one is used very rarely, events added to it get processed on average sooner than the ones added to the normal queue. (We can't starve the normal queue, so both need to be processed) MemoryPressure seems to want to really processed before any new task, so the new system can't be used for that. Looks like memory pressure works only on some platforms. On 11/10/2016 03:25 PM, Gabriele Svelto wrote: On 10/11/2016 00:22, smaug wrote: Parent process doesn't yet have higher priority handling [2]. Need to fix racy tests first. Locally using higher priority also in parent process seems to make tab throbber smoother. We have an ad-hoc mechanism for scheduling memory pressure event ahead of all other pending tasks [1]. Do you think we could use this new functionality to replace it? It would be nice to have this handled via a generic mechanism too. Gabriele [1] https://dxr.mozilla.org/mozilla-central/rev/336759fad4621dfcd0a3293840edbed67018accd/xpcom/threads/nsThread.cpp#1444 ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
Re: [e10s] Higher priority handling for vsync in child processes
On 10/11/2016 18:12, smaug wrote: > vsync handling happens usually right after a task (per HTML spec). > Basically we have now two event queues with similar priority, and they > are handled the same priority, but since > the other one is used very rarely, events added to it get processed on > average sooner than the ones added to the normal queue. > (We can't starve the normal queue, so both need to be processed) > > MemoryPressure seems to want to really processed before any new task, so > the new system can't be used for that. Thanks for clearing that up. > Looks like memory pressure works only on some platforms. Yes, only on Windows and Android AFAIK, and the former has some serious issues when it kicks in (which almost never happens BTW, we tend to OOM-crash well before it does). Gabriele signature.asc Description: OpenPGP digital signature ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
Re: [e10s] Higher priority handling for vsync in child processes
On 10/11/2016 00:22, smaug wrote: > Parent process doesn't yet have higher priority handling [2]. > Need to fix racy tests first. > Locally using higher priority also in parent process seems to make tab > throbber smoother. We have an ad-hoc mechanism for scheduling memory pressure event ahead of all other pending tasks [1]. Do you think we could use this new functionality to replace it? It would be nice to have this handled via a generic mechanism too. Gabriele [1] https://dxr.mozilla.org/mozilla-central/rev/336759fad4621dfcd0a3293840edbed67018accd/xpcom/threads/nsThread.cpp#1444 signature.asc Description: OpenPGP digital signature ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
[e10s] Higher priority handling for vsync in child processes
Hi, the latest nightly has higher priority for vsync/refreshDriver/requestAnimationFrame handling in child processes [1], which should make rendering updates smoother, at least in some cases. If you see any unexpected behavior, please file bugs and CC me, :smaug. And if there are cases when responsiveness feels now significantly better, I'd be curious to know about those too. Parent process doesn't yet have higher priority handling [2]. Need to fix racy tests first. Locally using higher priority also in parent process seems to make tab throbber smoother. -Olli [1] https://bugzilla.mozilla.org/show_bug.cgi?id=1306591 [2] https://bugzilla.mozilla.org/show_bug.cgi?id=1315570 ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
