Closed
Bug 1345002
Opened 7 years ago
Closed 3 years ago
(meta) Android performance issues on rendering page
Categories
(Firefox for Android Graveyard :: General, enhancement, P3)
Tracking
(Performance Impact:none)
RESOLVED
INCOMPLETE
Performance Impact | none |
People
(Reporter: atsai, Unassigned)
References
()
Details
Attachments
(3 files)
After a series of testing, we found that Fennec are 3x ~ 6x slower than other browsers on Android for loading a webpage. You can reference the URL of the bug. Since the links of test results may be removed by provider, here's the reproduce step. 1. Go to https://www.webpagetest.org/ 2. Enter the website you want to test 3. Select a location of devices. We use "Dulles, VA USA (Desktop,Android,iOS 9)". 4. Rest settings: (should be there by default) - Connection: Mobile LTE (12Mbps/12 Mbps 70ms RTT) - Number of test run: 9 - First View and Repeat View: check - Capture Video: check 5. Click on "START TEST"
Reporter | ||
Comment 1•7 years ago
|
||
If we want to start from some specific examples, I'll suggest to start with reddit.com and espn.com. Both of these two websites have many javascript scripts to control the layout. it should be worthwhile to take a look into it.
Comment 2•7 years ago
|
||
I wonder if we can have SME to look into this.
Flags: needinfo?(kanru)
Flags: needinfo?(bchien)
Comment 3•7 years ago
|
||
Hi Al, On the other hand, how about running similar benchmark testings but on google suites? (assuming doing this via WPT is easy) Those are where we have more people digging into. See Bug 1336173
Comment 4•7 years ago
|
||
Is it possible to have profile data for all of your test pages? Ref: https://developer.mozilla.org/en-US/docs/Mozilla/Performance/Profiling_with_the_Built-in_Profiler#Profiling_Firefox_mobile
Flags: needinfo?(whuang)
Flags: needinfo?(kanru)
Flags: needinfo?(bchien)
Comment 5•7 years ago
|
||
(In reply to Bobby Chien [:bchien] from comment #4) > Is it possible to have profile data for all of your test pages? > > Ref: > https://developer.mozilla.org/en-US/docs/Mozilla/Performance/ > Profiling_with_the_Built-in_Profiler#Profiling_Firefox_mobile :atsai is aware of this. We'll see how to move it forward.
Flags: needinfo?(whuang)
Comment 6•7 years ago
|
||
Let's use this as a meta bug. We can create separate bugs blocking this, with some more specific details and profiler data.
Reporter | ||
Comment 7•7 years ago
|
||
I've setup gecko profiler for Firefox on Android on my local environment. I don't see the point to generate all websites in the sheet. Let's start with the three websites Firefox performs with issues: att.com, reddit.com, and espn.com.
Reporter | ||
Comment 8•7 years ago
|
||
Reporter | ||
Comment 9•7 years ago
|
||
Reporter | ||
Comment 10•7 years ago
|
||
Updated•7 years ago
|
Whiteboard: [qf]
Updated•7 years ago
|
Whiteboard: [qf] → [qf-]
Comment 12•7 years ago
|
||
Hi Jean, Was this one being minus per the qf triage? Just want to know why this is not prioritized.
Comment 13•7 years ago
|
||
We marked during qf triage. This is [qf-] because generally QF doesn't track mobile performance and this is a meta bug. If there are more specific performance bugs you could still nominate them.
[triage] Bulk edit from title: this is a non-critical issue or [meta] bug.
Priority: -- → P3
Comment 15•3 years ago
|
||
We have completed our launch of our new Firefox on Android. The development of the new versions use GitHub for issue tracking. If the bug report still reproduces in a current version of [Firefox on Android nightly](https://play.google.com/store/apps/details?id=org.mozilla.fenix) an issue can be reported at the [Fenix GitHub project](https://github.com/mozilla-mobile/fenix/). If you want to discuss your report please use [Mozilla's chat](https://wiki.mozilla.org/Matrix#Connect_to_Matrix) server https://chat.mozilla.org and join the [#fenix](https://chat.mozilla.org/#/room/#fenix:mozilla.org) channel.
Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → INCOMPLETE
Assignee | ||
Updated•3 years ago
|
Product: Firefox for Android → Firefox for Android Graveyard
Updated•2 years ago
|
Performance Impact: --- → -
Whiteboard: [qf-]
You need to log in
before you can comment on or make changes to this bug.
Description
•