Open Standard8 opened 6 years ago
I can take this. I did all this stuff for Screenshots.
Base commit with Talos jobs: https://treeherder.mozilla.org/#/jobs?repo=try&revision=0d75aa9246a904480470ec0eafab6fb7589d3d61
Talos run with min-vid shield study branch + moz.build file, no performance optimizations: https://treeherder.mozilla.org/#/jobs?repo=try&revision=efef136c524244832c1e962cf339cb41b8a6a068
Comparison between this and the base: https://treeherder.mozilla.org/perf.html#/compare?originalProject=try&originalRevision=0d75aa9246a904480470ec0eafab6fb7589d3d61&newProject=try&newRevision=efef136c524244832c1e962cf339cb41b8a6a068&framework=1
Here's a Talos run with the sessionstore-windows-restored
delay added: https://treeherder.mozilla.org/#/jobs?repo=try&revision=2d4a9f2c702f7103c5a567b1673907f36e7cc3c7
Comparison between this and the base: https://treeherder.mozilla.org/perf.html#/compare?originalProject=try&originalRevision=0d75aa9246a904480470ec0eafab6fb7589d3d61&newProject=try&newRevision=2d4a9f2c702f7103c5a567b1673907f36e7cc3c7&framework=1
Oh no! I applied these patches on top of mozilla-central, but min-vid doesn't work in Nightly.
I'll have to figure out which commit / branch is the correct base for current release channel, then re-run the Talos tests there :-\
Re-running Talos tests on top of the FIREFOX_59_0_RELEASE tag. mach
couldn't find artifacts for a commit this old, so I'm modifying the try incantation to remove the --artifact
argument:
try: -b o -p linux64,linux64-pgo,macosx64,win32,win32-pgo,win64,win64-pgo -u none -t all --rebuild 6
Base commit: https://treeherder.mozilla.org/#/jobs?repo=try&revision=febd1a18cbce90f99f95f303c379ba0dff7abb64 Min-Vid without startup delay: https://treeherder.mozilla.org/#/jobs?repo=try&revision=b80aff44b15dc684202645eb9f92b616bb691903 Min-Vid with startup delay: https://treeherder.mozilla.org/#/jobs?repo=try&revision=a649cfd06b617538dcb3db023486ff41be5c8f7c
Hmm. Adding a startup delay does not seem to resolve the Talos perf issues:
Splitting the problem space to try to understand the source of the regressions:
It seems like this might not get out before 60 goes to release on 5/9, so here's the same set of patches as Try runs against the release 60 base commit:
Still seeing the huge tp5o regressions with content scripts totally disabled in 59 (content_scripts section removed from the manifest):
OK, starting to narrow down a little.
Something either in the StudyUtils.jsm code, or in our use of that code, seems to be causing a lot of the performance problems.
Here's a screenshot of the tp5o regressions on Firefox 59 + minvid + startup delay (results page):
If the code that loads and uses StudyUtils.jsm is removed, there are fewer reds, but still a lot of oranges ([results page]()):
More detail below, for later reference.
Today, I kicked off Talos runs testing three different changes on both minvid+59 and minvid+60:
Here are the corresponding Try runs:
Talos run against just 59, no minvid: https://treeherder.mozilla.org/#/jobs?repo=try&revision=febd1a18cbce90f99f95f303c379ba0dff7abb64
Talos run against just 60, no minvid: https://treeherder.mozilla.org/#/jobs?repo=try&revision=ed1ceac6daf75a270cc96511e5dffbbf3a1c48ea
Here's a new run, with StudyUtils removed and where the embedded webextension is never started:
on 59: https://treeherder.mozilla.org/#/jobs?repo=try&revision=acd21af2719779fac4ab04a0d50cc1a0f921d597
on 60: https://treeherder.mozilla.org/#/jobs?repo=try&revision=46c310a5fa60b1df3efb171bd68f1e1cd23be608
The last run against 60 produced some inexplicable performance improvements, so I'm re-running everything now:
The basic summary of what to do is:
try: -b o -p linux64,linux64-pgo,macosx64,win32,win32-pgo,win64,win64-pgo -u none -t all --artifact --rebuild 6
(not you need at least 6 rebuilds for enough comparisons, you may need a few retriggers as well). You should also be able to get away with artifact builds.Once the results come in, they'll appear on the comparison page, and you'll want to look for any red or yellow changes.
For building into mozilla-central. The easiest way is to copy what happens in one of the browser/extensions/ folders of the system add-ons - probably the screenshots one.
If you need more help or have questions, feel free to ping me.