Closed Bug 1602657 Opened 6 years ago Closed 5 years ago

Set appropriate value for post-startup-delay in (and only in) CI, for conditioned-profile runs

Categories

(Testing :: Raptor, enhancement, P1)

Version 3
enhancement

Tracking

(firefox75 fixed)

RESOLVED FIXED
mozilla75
Tracking Status
firefox75 --- fixed

People

(Reporter: stephend, Assigned: tarek)

References

(Blocks 4 open bugs)

Details

(Keywords: perf-alert, Whiteboard: [ci-costs-2020:done])

Attachments

(1 file)

As generally agreed on in today's Browsertime triage meeting, let's do the following, for post-startup-delay:

  • if in CI, and running on a known conditioned-profile enabled platform/build variant, automatically set/apply post-startup-delay = to a known, agreed-upon value (likely not 0; we'll need to test) which we're happy with, for abating browser settle-time
  • if we're running locally, just respect the value of post-startup-delay (if present); else, do nothing (advanced users can and will know to add that, and we can document better, too)

--
Currently, via bug 1596346, we're doing this automatically in all environments, but I'm removing that (https://searchfox.org/mozilla-central/rev/23d4bffcad365e68d2d45776017056b76ca9a968/testing/raptor/raptor/raptor.py#175-178) over in bug 1600838.

Priority: -- → P1
Attachment #9116534 - Attachment description: Bug 1602657 - [WIP] Set appropriate value for post-startup-delay in (and only in) CI, for conditioned-profile runs. r?#perftest → Bug 1602657 - Set appropriate value for post-startup-delay in (and only in) CI, for conditioned-profile runs. r?#perftest

Latest try push below, which still fails unittests; I'd love feedback/help, to get this in soon, and correctly :-)

https://treeherder.mozilla.org/#/jobs?repo=try&tier=1%2C2%2C3&revision=a4594152de18a5cb3f8fab2bc9ec5e69b11da231

Attachment #9116534 - Attachment description: Bug 1602657 - Set appropriate value for post-startup-delay in (and only in) CI, for conditioned-profile runs. r?#perftest → Bug 1602657 - Set appropriate value for post-startup-delay in (and only in) CI, for conditioned-profile runs. r?#perftest, r?rwood
Attachment #9116534 - Attachment description: Bug 1602657 - Set appropriate value for post-startup-delay in (and only in) CI, for conditioned-profile runs. r?#perftest, r?rwood → Bug 1602657 - Set appropriate value for post-startup-delay in (and only in) CI, for conditioned-profile runs. r?#perftest,rwood
Attachment #9116534 - Attachment description: Bug 1602657 - Set appropriate value for post-startup-delay in (and only in) CI, for conditioned-profile runs. r?#perftest,rwood → Bug 1602657 - Set appropriate value for post-startup-delay in (and only in) CI, for conditioned-profile runs. r?#perftest, r?rwood

This should now be ready for review, again; the most-recent try push with added logging, here: https://treeherder.mozilla.org/#/jobs?repo=try&tier=1%2C2%2C3&revision=4c3d64ab9d47e81942e772826890ed21df9fed3b

Attachment #9116534 - Attachment description: Bug 1602657 - Set appropriate value for post-startup-delay in (and only in) CI, for conditioned-profile runs. r?#perftest, r?rwood → Bug 1602657 - Set appropriate value for post-startup-delay in (and only in) CI, for conditioned-profile runs. r?#perftest,rwood

I also did a try push from vanilla mozilla-central, to suss out the intermittents on Browsertime mobile (tp6m-c-1) seen in the previous push; they are still there, so should be unrelated to this patch: https://treeherder.mozilla.org/#/jobs?repo=try&tier=1%2C2%2C3&revision=d8368dd28bd0488364b6d92eda2a773381577c50

Pushed by sdonner@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/80f5c59d5df4 Set appropriate value for post-startup-delay in (and only in) CI, for conditioned-profile runs. r=perftest-reviewers,rwood
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla73

Backed out changeset 80f5c59d5df4 (Bug 1602657) as requested by sdonner on slack.
https://hg.mozilla.org/integration/autoland/rev/325da10270e4bbc644df0fd29a6c3f6ef536d262

Status: RESOLVED → REOPENED
Flags: needinfo?(stephen.donner)
Resolution: FIXED → ---
Target Milestone: mozilla73 → ---
Flags: needinfo?(stephen.donner) → needinfo?(aionescu)

Hey Stephen! Looks like the revision from [1] in the compare link doesn't have the same commit hash. In the compare link you used b702ce549a0efe21164dc4966931c08e3b9c5573 but in the jobs link from [1] the revision is d8c9d60cc8f6a94e8b594f9853c2d7553683555f
This should be the correct comparison, except you don't really have the same jobs triggered, but I will take care of that. By the time you come back to office you should have the data you need.
PS: I am going to write a document about how the compare view can be used. It is WIP for the moment

Flags: needinfo?(aionescu)
Assignee: stephen.donner → tarek

performance comparisons

52d0976feda8b1f2061cad0ea4eef647bd481067 == original
352cb828808e63cead3206c3c60162dc241c61c5 == post_startup_delay = 1000
6bd2031e761083cacb6bc5b21b84ecfe6ff0cbc1 == post_startup_delay = 5000
bea7d8f0cde25a7b50cadb271ac428c065dffd69 == post_startup_delay = 15000
45f3987c34bb4152e0476276f992940dddf5753e == post_startup_delay == 30000 (if we see changes in this one, something's broken)

30s vs 1s :
https://treeherder.mozilla.org/perf.html#/compare?originalProject=try&originalRevision=52d0976feda8b1f2061cad0ea4eef647bd481067&newProject=try&newRevision=352cb828808e63cead3206c3c60162dc241c61c5&framework=10&pageTitle=post+startup+delay+-+30s+vs+1s

30s vs 5s :
https://treeherder.mozilla.org/perf.html#/compare?originalProject=try&originalRevision=52d0976feda8b1f2061cad0ea4eef647bd481067&newProject=try&newRevision=6bd2031e761083cacb6bc5b21b84ecfe6ff0cbc1&framework=10&pageTitle=post+startup+delay+-+30s+vs+5s

30s vs 15s :
https://treeherder.mozilla.org/perf.html#/compare?originalProject=try&originalRevision=52d0976feda8b1f2061cad0ea4eef647bd481067&newProject=try&newRevision=bea7d8f0cde25a7b50cadb271ac428c065dffd69&framework=10&pageTitle=post+startup+delay+-+30s+vs+15s

30s vs 30s
https://treeherder.mozilla.org/perf.html#/compare?originalProject=try&originalRevision=52d0976feda8b1f2061cad0ea4eef647bd481067&newProject=try&newRevision=45f3987c34bb4152e0476276f992940dddf5753e&framework=10&pageTitle=post+startup+delay+-+30s+vs+30s
Sorry I did not filter out chrome/chromium runs...

Depends on: 1612790
Status: NEW → ASSIGNED

I think we have enough data at this point with the current quality of our recording. I'll defer the final decision to Dave before landing

Flags: needinfo?(dave.hunt)

The only concern I have is the improvement we see on macOS (7-14%). Bebe: could you rebase and push to try just for macOS with screenshots enabled? This will give us the confidence value to compare and show us if there are any major visual differences when changing the post startup delay.

Flags: needinfo?(dave.hunt) → needinfo?(fstrugariu)

Bebe, your push has some code failures

Flags: needinfo?(fstrugariu)
Flags: needinfo?(tarek)

Looked at the screenshots and all seems OK

Flags: needinfo?(dave.hunt)
Attachment #9116534 - Attachment description: Bug 1602657 - Set appropriate value for post-startup-delay in (and only in) CI, for conditioned-profile runs. r?#perftest,rwood → Bug 1602657 - Set appropriate value for post-startup-delay in CI
Attachment #9116534 - Attachment description: Bug 1602657 - Set appropriate value for post-startup-delay in CI → Bug 1602657 - Set appropriate value for post_startup_delay in CI
Pushed by tziade@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/1a28609bb405 Set appropriate value for post_startup_delay in CI r=perftest-reviewers,Bebe
Flags: needinfo?(dave.hunt)
Status: ASSIGNED → RESOLVED
Closed: 5 years ago5 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla75
Regressions: 1619167
Whiteboard: [ci-costs-2020:done]
Keywords: perf-alert
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: