Consider increasing the priority of the runnables involved in the loading of geckoview.xhtml
Categories
(Core :: Networking, task, P2)
Tracking
()
People
(Reporter: acreskey, Unassigned)
References
(Blocks 4 open bugs)
Details
(Whiteboard: [necko-triaged])
Loading the chrome url, geckoview.xhtml, is on the critical path of Fenix startup.
Based on Markus' analysis in https://bugzilla.mozilla.org/show_bug.cgi?id=1960712 we see a chain of runnables that could be prioritized to potentially reduce the time it takes to load the blocking geckoview.xhtml.
|
Reporter | |
Updated•3 months ago
|
|
|
Reporter | |
Comment 1•3 months ago
•
|
||
I've tried to increase the priority of the runnables; no clear improvements yet so I think these will have to be profiled to see what's happening.
• Increase priority of the Jar channel load compare
• nsAsyncRedirectVerifyHelper and callback compare
• Set render_blocking priority of asyncOnChannelRedirect from WebRequest.sys.mjs
Regression?
compare
• Increase priority of the PDocumentChannel RedirectToRealChannel message
PGO Build timeout?
compare
• nsAsyncRedirectVerifyHelper and callback + JarChannel load
compare
Description
•