Closed
Bug 1176237
Opened 9 years ago
Closed 9 years ago
[raptor] reduce variance to help eliminate falsely-detected regressions on gaia-ci
Categories
(Firefox OS Graveyard :: Gaia::PerformanceTest, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
FxOS-S4 (07Aug)
People
(Reporter: rwood, Assigned: rwood)
References
Details
Attachments
(2 files)
The raptor launch test is running on all apps on gaia-ci, but not currently posting to treeherder due to variance and false alarms. Investigate and try ways to reduce variance and ideally have zero falsely-detected performance regressions. The variance between aws instances, even though the same instance type, is the core cause. Confirmed by :ekyle by plotting raw raptor data. Try running the base and base+patch tasks on the same instance instead of separate instances for each, that will help. Also when taskcluster support for ramdisks is available, running the emulator on a ramdisk will help also.
Comment 1•9 years ago
|
||
Assignee | ||
Comment 2•9 years ago
|
||
Change the raptor graph decision code to create a single raptor task per app. Use the new raptor-gaia docker image. Once this is merged, I will be requesting the treeherder folks to hide the newly-named raptor tasks until the tweaks are completed.
Attachment #8631232 -
Flags: review?(garndt)
Assignee | ||
Comment 3•9 years ago
|
||
Comment on attachment 8631232 [details] [review] https://github.com/mozilla-b2g/gaia/pull/30882 Greg is on PTO, John would you have some time for a review please? This is step 1, changing to a single task per app for the raptor launch test. Once this is merged I'll be hiding the tasks on treeherder until it is finished up.
Attachment #8631232 -
Flags: review?(garndt) → review?(jhford)
Assignee | ||
Comment 4•9 years ago
|
||
Comment on attachment 8631232 [details] [review] https://github.com/mozilla-b2g/gaia/pull/30882 Back to Greg as he's back and has done the Raptor-related reviews in the past, thanks
Attachment #8631232 -
Flags: review?(jhford) → review?(garndt)
Comment 5•9 years ago
|
||
Comment on attachment 8631232 [details] [review] https://github.com/mozilla-b2g/gaia/pull/30882 looks good, if this works for you then sheeep it side note: noticed that in your new raptor docker image there is an entrypoint specified that doesn't appear to exist unless I'm overlooking it.
Attachment #8631232 -
Flags: review?(garndt) → review+
Assignee | ||
Comment 6•9 years ago
|
||
Thanks Greg. Landed: https://github.com/mozilla-b2g/gaia/commit/c2c798dd2faadc49c5440abaa60fb2ea3f57113f
Status: NEW → ASSIGNED
Assignee | ||
Comment 7•9 years ago
|
||
Update: In the last 50 Raptor suite runs on gaia and gaia-master, there have been zero falsely-flagged regressions. Also, the test of introducing an intentional app launch regression and having Raptor catch it, was a success (see Bug 1171167). So far these results look good, a definite improvement. Awaiting feedback from :ekyle on the data also, and will keep an eye on the trees.
Assignee | ||
Comment 8•9 years ago
|
||
Received detailed feedback from :ekyle on some analysis he did on some of the Raptor gaia-ci data. Taking that feedback into consideration, and looking at the Raptor suite runs on gaia-ci thus far, I believe the refactored automation is looking good. Due to the nature of running performance tests on the emulator, in docker, on aws taskcluster workers, etc, there will always be some variance and therefore we are limited to the sensitivity of regression that can be detected. With the current setup, number of app launches, and automatic retries, it looks like detecting a 15% or higher regression on gaia-ci is valid. Regressions smaller than that should be detected on the Raptor tests running on-device post-commit. There will always be room for improvement and we can make tweaks down the road, for instance when ramdisk support is added to taskcluster workers. The new Raptor tasks are now visible on treeherder (gaia and gaia-master) by default.
Status: ASSIGNED → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Updated•9 years ago
|
Target Milestone: --- → FxOS-S4 (07Aug)
You need to log in
before you can comment on or make changes to this bug.
Description
•