Performance experiment: create the speculative gecko session sooner to improve applink (view) startup
Categories
(Fenix :: Performance, defect)
Tracking
(Performance Impact:low)
Performance Impact | low |
People
(Reporter: cpeterson, Unassigned)
Details
From github: https://github.com/mozilla-mobile/fenix/issues/15973.
The idea behind the experiment:
Create the gecko engine session as soon as possible in order to improve applink (view) startup time.Since the view test (measuring navigation start and loadEvent) depends on the gecko engine and the content process if we can instantiate the gecko engine sooner, we may be able to improve our timings.
Procedure
Create a speculative gecko engine session in FenixApplication
OnCreate()
components.core.engine.speculativeCreateSession(false)
Results
No measured difference:
Variant Median, navStart Median, loadEventEnd Baseline 2420 5496 Experiment 2420 5526 Experiment:
https://docs.google.com/spreadsheets/d/1lu_c0hZGMzMpqGuEb8wtA8hwEucItiy-Uf8gpWUYVmo/edit#gid=0&range=B24:G45┆Issue is synchronized with this Jira Task
Change performed by the Move to Bugzilla add-on.
Comment 1•2 years ago
|
||
The severity field is not set for this bug.
:cpeterson, could you have a look please?
For more information, please visit auto_nag documentation.
Updated•1 year ago
|
Comment 2•1 year ago
|
||
The Performance Impact Calculator has determined this bug's performance impact to be low. If you'd like to request re-triage, you can reset the Performance Impact flag to "?" or needinfo the triage sheriff.
Platforms: Android
Impact on browser: Causes noticeable jank
Websites affected: Rare
Comment 3•1 year ago
•
|
||
duplicate comment
Updated•10 months ago
|
Description
•