Visual metrics: Fenix is significantly slower than Chrome for the site https://www.reddit.com
Categories
(Core :: Performance, defect, P2)
Tracking
()
Performance Impact | medium |
People
(Reporter: acreskey, Unassigned, NeedInfo)
Details
(Keywords: perf:pageload, perf:responsiveness, top50)
Attachments
(2 files)
Fenix is significantly slower than Chrome 76 on visual metrics for the site https://www.reddit.com
For instance, the median SpeedIndex in Chrome was 1723, while in Fenix with Strict tracking protection it was found to be 2226 and 2379 with tracking protection disabled.
Results here (cold page load, live sites, Pixel 3)
This was also seen in a July 2019 visual metrics pass, Pixel 2.
This video compares Chrome and Fenix with Tracking Protection off and strict mode.
Comment 1•5 years ago
|
||
This is probably a dup of bug 1574024
Reporter | ||
Updated•5 years ago
|
Updated•5 years ago
|
Updated•4 years ago
|
Comment 2•4 years ago
|
||
We ran some browsertime tests against different Ion tiers, and it turned out the compiler wasn't the problem
Detail results
https://docs.google.com/spreadsheets/d/1rd7r70yXjuBF54bjMnIT6bQNM6vd2ejPmEjK_s6zVjc/edit?usp=sharing
Reporter | ||
Comment 3•3 years ago
|
||
As in Bug 1583220, the latest data I have comparing Fenix and Chrome on https://www.reddit.com is from Fenix Beta, Dec 18, 2020.
https://docs.google.com/spreadsheets/d/18qCiz3SReDgDPwhbYfuDrbnBK1030FuVWGBHWwdgCFY/edit#gid=96892842&range=360:360
While Fenix was faster in visual metrics than Fennec68, Chrome84 was still faster on https://www.reddit.com
Reporter | ||
Comment 4•3 years ago
|
||
I'll find out if this is still the case.
Reporter | ||
Comment 5•3 years ago
|
||
It looks like this is still the case - Chrome is reproducibly faster than Fenix on vismets.
I used this url for content stability:
https://www.reddit.com/r/firefox/
Reporter | ||
Comment 6•3 years ago
|
||
Actually, I haven't been able to reproduce a significant difference between Chrome and Fenix.
https://docs.google.com/spreadsheets/d/18qCiz3SReDgDPwhbYfuDrbnBK1030FuVWGBHWwdgCFY/edit#gid=2085165784&range=42:42
I've captured profiles that we'll examine just to see if anything stands out.
Comment 7•3 years ago
|
||
Unassign myself as I am not actively working on it.
I took a manual side-by-side videos on different days and got the following results:
Date | Chrome | Fenix | Diff |
---|---|---|---|
10/14 | 5700ms | 8600ms | 2900ms |
11/3 #1 | 7966ms | 7666ms | -300ms |
11/3 #2 | 8133ms | 6333ms | -1800ms |
Curiously, Chrome got slower today than the previous test date – I wonder if the page contents or my network conditions changed.
One major difference between the videos is that Firefox's first paint (to the reddit loading icon) is much faster on 11/3 than it was on 10/14.
Reporter | ||
Updated•2 years ago
|
Spoke with acreskey: now that we can't reproduce such a large difference, the next step is to check the cause. We should try setting dom.script_loader.full_parse_max_size
to 0 and comparing the results to see if the full parse was helpful.
Updated•2 years ago
|
Comment 12•2 years ago
|
||
Performance P1 should also be S2 severity (at least).
Comment 13•2 years ago
|
||
The Performance Priority Calculator has determined this bug's performance priority to be P1. If you'd like to request re-triage, you can reset the Performance flag to "?" or needinfo the triage sheriff.
Platforms: Android
Impact on site: Causes noticeable jank
Page load impact: Some
Websites affected: Major
Comment 14•1 year ago
|
||
Frank, according to comment 11 this was no longer reproducible. Should we close it or re-test?
Comment 15•1 year ago
|
||
:mleclair, is this something that we'd be able to measure going off of mcomella's last update in Comment 11? If so, could be worth tracking for the future. If you feel that this is too old or not reproducible, we can close
Reporter | ||
Comment 16•1 year ago
|
||
I'm trying to collect some numbers on these via our performance tests since we have support for live sites Fenix and Chrome.
(along with Bug 1583220)
Currently blocked on Bug 1780817, but it looks like it's progressing well.
Reporter | ||
Comment 17•1 year ago
|
||
Our live-site Android tests have been fixed.
Unfortunately this still looks to be an issue.
https://treeherder.mozilla.org/jobs?repo=try&selectedTaskRun=ItAk-jtGSJyY6vQyd02aFQ.0&tier=1%2C2%2C3&revision=8bdcd80751cdce6f835351ea40fa7e2667143e60
Chrome shows reproducibly better visual metrics than Fenix on reddit.com.
From a look at the video recordings, the results are valid.
I suggest we take some of the profiles to JoyOfProfiling sessions to see if we can spot any issues.
Reporter | ||
Updated•7 months ago
|
Comment 18•6 months ago
|
||
Jamie, could you create a comparison report of loading reddit.com?
Comment 19•6 months ago
|
||
Updated•5 months ago
|
Comment 20•5 months ago
|
||
Not enough data to show that this reproduces locally. Tried this on my Pixel 8 and while cold load was slower (though not significantly), performed just as well on warm load. Calculator shows a High (75) score. Gut feeling is this is a Medium impact.
A profile with more data would be required to make this a more significant impact
The Performance Impact Calculator has determined this bug's performance impact to be high. If you'd like to request re-triage, you can reset the Performance Impact flag to "?" or needinfo the triage sheriff.
Platforms: Android
Page load impact: Some
Websites affected: Major
[x] Able to reproduce locally
Asking :mleclair to grab a profile and a new video comparison
Comment 21•5 months ago
|
||
Given the lowered performance impact, we should reduce severity.
Comment 22•5 months ago
|
||
Comment 23•5 months ago
|
||
(In reply to Marco Castelluccio [:marco] from comment #21)
Given the lowered performance impact, we should reduce severity.
Frank, do you agree?
Updated•5 months ago
|
Description
•