[meta][project] Improve page load performance

NEW
Unassigned

Status

()

Firefox for Android
General
4 years ago
2 years ago

People

(Reporter: mcomella, Unassigned)

Tracking

(Depends on: 8 bugs, {meta, perf})

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

4 years ago
In the 12/4 weekly meeting [1], we discussed a gradual performance regression in page load times over the past few months, discovered by comparisons to Chrome and Eideticker.

Currently, we can track page load time with the full product by loading a page and comparing the result with older versions. This is a good start but we should also create a method of determining how much page load performance is impacted by Android-specific code so we can find regressions there.

For example, one suggestion is to build Gecko into a standalone app (perhaps using GeckoView) that will startup and immediately load some web page, and compare this to our full app results (ex: Eideticker).

There may also be work to be done on profiling and seeing where we might be slow, perhaps independently from whether we have regressed or not. For example, there may be some inefficiencies where code is called multiple times ([2], [3]).

Finally, there is work to be done on page load performance that is not a direct regression, such as predictive lookup and prefetching (see [4] and its blocking bugs).

[1]: https://wiki.mozilla.org/Mobile/Notes/04-Dec-2013
[2]: https://bugzilla.mozilla.org/show_bug.cgi?id=924712
[3]: https://bugzilla.mozilla.org/show_bug.cgi?id=941844
[4]: https://bugzilla.mozilla.org/show_bug.cgi?id=943475
No longer blocks: 943475
Depends on: 916968, 943475
Keywords: meta
(Reporter)

Updated

4 years ago
Depends on: 947393
(Reporter)

Updated

4 years ago
Depends on: 941155
(Reporter)

Updated

4 years ago
Depends on: 948565
Adding a few of the redirect bugs that make GlobalHistory do less work during a pageload. Less writing to the DB means more time for networking.

Also adding the Seer pageload regression.
Depends on: 949913, 949104, 949639, 945779
Depends on: 945408
Depends on: 951959
Depends on: 952799
Depends on: 952878
I think this bug is/has morphed into the tracking bug for the page load performance project, so gently recasting it as such, under the assumption that some of "improve" will be "find and fix regressions".

mfinkle, do we still not track meta bugs? Is the weekly meeting enough spinning for these project 'plates'?
Depends on: 947067
Summary: [meta] Investigate page load performance and regression → [meta][project] Improve page load performance
Depends on: 952894
Depends on: 955870
Depends on: 952473
Depends on: 917896
(Reporter)

Updated

4 years ago
Depends on: 954008
(Reporter)

Updated

4 years ago
No longer depends on: 954008
Depends on: 957037
Depends on: 958087
Depends on: 924712
(Reporter)

Updated

4 years ago
Depends on: 964307
Depends on: 899424
Depends on: 899425
Depends on: 966573
Depends on: 963505
Depends on: 969835
Depends on: 970604
Depends on: 971232
Depends on: 971239
You need to log in before you can comment on or make changes to this bug.