-
#REDIRECT [[Performance/Tools/FAQ]]
== What is Perfherder? ==
23 KB (3,896 words) - 16:26, 24 July 2023
-
{{DISPLAYTITLE:Performance Tools FAQ}}
{{DISPLAYTITLE:Performance Tools FAQ}}
23 KB (3,900 words) - 10:08, 16 November 2023
-
#REDIRECT [[TestEngineering/Performance/Sheriffing]]
...ealt with. They look at the data produced by performance test jobs (mainly Talos), find regressions, determine their root cause(s) and gets bugs on file to
12 KB (2,017 words) - 13:05, 6 August 2019
-
...ealt with. They look at the data produced by performance test jobs (mainly Talos), find regressions, determine their root cause(s) and gets bugs on file to
A short demo describing the performance sheriffing workflow:
11 KB (1,920 words) - 11:44, 16 March 2021
-
...Perfherder]. Any time a test or tests exceed [[TestEngineering/Performance/Sheriffing/Workflow#Thresholds|the set threshold for its framework]], one or multiple
...riff(and have sheriffing permissions) you will need to file 2 bugs to have sheriffing actions allowed in treeherder.
37 KB (6,028 words) - 15:45, 4 March 2024
-
#REDIRECT [[TestEngineering/Performance/Sheriffing/Perfherder FAQ]]
= What is Perfherder =
4 KB (790 words) - 13:18, 6 August 2019
-
...[[Performance FAQ|https://wiki.mozilla.org/TestEngineering/Performance/FAQ#Sheriffing]]
Linux and Windows builds have [[TestEngineering/Performance/Sheriffing/Tree_FAQ#What_is_PGO|PGO]], OSX does not.
7 KB (1,153 words) - 13:54, 16 January 2020
-
...eeherder. This project is called Perfherder. We'd like discuss plans for Perfherder, and get some input from potential users of it.
== FAQ ==
27 KB (4,375 words) - 01:30, 9 August 2021
-
#REDIRECT [[TestEngineering/Performance/Sheriffing/Alert_FAQ]]
= FAQ =
2 KB (403 words) - 13:14, 6 August 2019
