TestEngineering/Performance/Sheriffing/Tree FAQ: Difference between revisions

TestEngineering/Performance/Sheriffing/Tree FAQ (view source)

2 bytes removed , 16 January 2018

remove extra brackets

160

edits

@@ Line 65: / Line 65: @@
 = What is PGO =
-PGO is [[https://developer.mozilla.org/en-US/docs/Building_with_Profile-Guided_Optimization Profile Guided Optimization]] where we do a build, run it to collect metrics and optimize based on the output of the metrics.  We only release PGO builds, and for the integration branches we do these periodically (6 hours) or as needed.  For Mozilla-Central we follow the same pattern.  As the builds take considerably longer (2+ times as long) we don't do this for every commit into our integration branches.
+PGO is [https://developer.mozilla.org/en-US/docs/Building_with_Profile-Guided_Optimization Profile Guided Optimization] where we do a build, run it to collect metrics and optimize based on the output of the metrics.  We only release PGO builds, and for the integration branches we do these periodically (6 hours) or as needed.  For Mozilla-Central we follow the same pattern.  As the builds take considerably longer (2+ times as long) we don't do this for every commit into our integration branches.
 How does this affect alerts?  We care most about PGO alerts- that is what we ship!  Most of the time an alert will be generated for a -Non-PGO build and then a few hours or a day later we will see alerts for the PGO build.