Open Bug 1807361 Opened 2 years ago Updated 1 year ago

~200ms until GeckoRuntime.create is called during COLD start up

Categories

(Fenix :: Performance, defect)

All
Android
defect

Tracking

(Performance Impact:none)

Performance Impact none

People

(Reporter: cpeterson, Unassigned)

Details

From github: https://github.com/mozilla-mobile/fenix/issues/9261.

Startup profile: https://perfht.ml/2WsFa0Z

In the profile, it took around 417ms until GeckoRuntime.create was called. The profile is from a debuggable build, so it's exaggerating the problem a little bit, but it shows a number of things getting initialized earlier.

The earlier GeckoRuntime.create is called, the earlier Gecko can kick off network requests. This improves the app link startup experience.

┆Issue is synchronized with this Jira Task

Change performed by the Move to Bugzilla add-on.

The severity field is not set for this bug.
:cpeterson, could you have a look please?

For more information, please visit auto_nag documentation.

Flags: needinfo?(cpeterson)
Flags: needinfo?(cpeterson)

Putting this as none for performance impact. However, it still is worthwhile to look at in the future I think. Mcomella did some work digging into it and I think it could be a good gain for startup

Performance Impact: --- → none
Severity: -- → S3
You need to log in before you can comment on or make changes to this bug.