Skip to content
This repository has been archived by the owner on Feb 20, 2023. It is now read-only.

HomeFragment is unexpectedly inflated on cold VIEW start up (was: 39-127ms COLD VIEW start up regression around 10/1) #21759

Closed
mcomella opened this issue Oct 6, 2021 · 2 comments
Assignees
Labels
perf:P1 must have/meet (VP prod must approve miss) performance Possible performance wins

Comments

@mcomella
Copy link
Contributor

mcomella commented Oct 6, 2021

This is a breakout from #21749.

We see a regression between 9/29 and 10/1:

  • VIEW: 39ms

The regression continues to rise. From 9/29 to 10/5, we see a regression of:

  • VIEW: 127ms

VIEW (note the scales are different):
image

This seems like it could be be two discrete regressions – one between 9/29 & 10/1 and one on 10/5. Dashboard link. The numbers seem a little noisy so let me know if you think it's worth retaking them. Maybe we should start with a profile though.

Profiles

VIEW:

One notable visual difference between these builds is the inclusion of Pocket content. There was also an update the synchronized the layouts for the homescreen. These could be the two events I mentioned above. However, this shouldn't affect the VIEW code path: let's find out what's going on.

┆Issue is synchronized with this Jira Task

@mcomella mcomella added performance Possible performance wins perf:P1 must have/meet (VP prod must approve miss) labels Oct 6, 2021
@mcomella mcomella added this to Needs triage in Performance, front-end roadmap via automation Oct 6, 2021
@github-actions github-actions bot added the needs:triage Issue needs triage label Oct 6, 2021
@csadilek
Copy link
Contributor

csadilek commented Oct 6, 2021

What we're seeing here is that the execution time of HomeFragment.onCreateView increased, which makes sense given that we added a lot of features to it recently. However, we shouldn't have to create this view to begin with, as the intention here is to launch into a tab.

csadilek added a commit to csadilek/fenix that referenced this issue Oct 7, 2021
…ng to tab

Co-authored-by: Sebastian Kaspari <s.kaspari@gmail.com>
@amedyne amedyne removed the needs:triage Issue needs triage label Oct 8, 2021
pocmo added a commit to csadilek/fenix that referenced this issue Oct 8, 2021
…ng to tab

Co-authored-by: Sebastian Kaspari <s.kaspari@gmail.com>
csadilek added a commit to csadilek/fenix that referenced this issue Oct 8, 2021
…ng to tab

Co-authored-by: Sebastian Kaspari <s.kaspari@gmail.com>
@MarcLeclair MarcLeclair moved this from Needs triage to Triaged (unordered) in Performance, front-end roadmap Oct 13, 2021
csadilek added a commit to csadilek/fenix that referenced this issue Oct 14, 2021
…ng to tab

Co-authored-by: Sebastian Kaspari <s.kaspari@gmail.com>
csadilek added a commit to csadilek/fenix that referenced this issue Oct 15, 2021
…ng to tab

Co-authored-by: Sebastian Kaspari <s.kaspari@gmail.com>
csadilek added a commit to csadilek/fenix that referenced this issue Oct 15, 2021
…ng to tab

Co-authored-by: Sebastian Kaspari <s.kaspari@gmail.com>
csadilek added a commit to csadilek/fenix that referenced this issue Oct 18, 2021
…ng to tab

Co-authored-by: Sebastian Kaspari <s.kaspari@gmail.com>
@csadilek csadilek added this to Ready for Engineering (min-5 ; max-22) in Android Engineering Team Kanban board via automation Oct 18, 2021
@csadilek csadilek removed this from Ready for Engineering (min-5 ; max-22) in Android Engineering Team Kanban board Oct 18, 2021
@csadilek csadilek added this to Security and Performance (top 10 issues) in Android Team Backlog Staging Board Oct 18, 2021
csadilek added a commit to csadilek/fenix that referenced this issue Oct 18, 2021
…ng to tab

Co-authored-by: Sebastian Kaspari <s.kaspari@gmail.com>
csadilek added a commit to csadilek/fenix that referenced this issue Dec 2, 2021
…ng to tab

Co-authored-by: Sebastian Kaspari <s.kaspari@gmail.com>
csadilek added a commit to csadilek/fenix that referenced this issue Dec 2, 2021
…ng to tab

Co-authored-by: Sebastian Kaspari <s.kaspari@gmail.com>
@mergify mergify bot closed this as completed in f919e97 Dec 8, 2021
Performance, front-end roadmap automation moved this from Triaged (unordered) to Done Dec 8, 2021
@mcomella mcomella changed the title 39-127ms COLD VIEW start up regression around 10/1 HomeFragment is unexpectedly inflated on cold VIEW start up (was: 39-127ms COLD VIEW start up regression around 10/1) Dec 8, 2021
@mcomella
Copy link
Contributor Author

mcomella commented Dec 13, 2021

The day after the PR #21805 landed, we measured an improvement of ~138ms to our COLD VIEW start up numbers. 🎉 This is similar to what I measured in my proof-of-concept measuring; #21805 (comment)

pkirakosyan pushed a commit to gexsi/user-agent-android that referenced this issue Mar 8, 2022
…ng to tab

Co-authored-by: Sebastian Kaspari <s.kaspari@gmail.com>
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
perf:P1 must have/meet (VP prod must approve miss) performance Possible performance wins
Projects
Android Team Backlog Staging Board
Security and Performance (top 10 issues)
Development

No branches or pull requests

4 participants