TestEngineering/Performance/Talos: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
|||
| Line 22: | Line 22: | ||
* Taskcluster runs a talos job on a hardware machine when one is available - this is bootstrapped by [https://searchfox.org/mozilla-central/source/testing/mozharness/mozharness/mozilla/testing/talos.py Mozharness] | * Taskcluster runs a talos job on a hardware machine when one is available - this is bootstrapped by [https://searchfox.org/mozilla-central/source/testing/mozharness/mozharness/mozilla/testing/talos.py Mozharness] | ||
** [https://searchfox.org/mozilla-central/source/testing/mozharness/mozharness/mozilla/testing/talos.py Mozharness\ downloads the build, talos.zip (found in [http://hg.mozilla.org/mozilla-central/tip/testing/talos/talos.json talos.json]), and creates a virtualenv for running the test. | ** [https://searchfox.org/mozilla-central/source/testing/mozharness/mozharness/mozilla/testing/talos.py Mozharness\ downloads the build, talos.zip (found in [http://hg.mozilla.org/mozilla-central/tip/testing/talos/talos.json talos.json]), and creates a virtualenv for running the test. | ||
** Mozharness [[ | ** Mozharness [[/Talos/Running#How_Talos_is_Run_in_Production|configures the test and runs it]] | ||
** After the test is completed the data is uploaded to [https://treeherder.mozilla.org/perf.html#/graphs PerfHerder] | ** After the test is completed the data is uploaded to [https://treeherder.mozilla.org/perf.html#/graphs PerfHerder] | ||
* Treeherder displays a green (all OK) status and has a link to the [https://treeherder.mozilla.org/perf.html#/graphs PerfHerder] | * Treeherder displays a green (all OK) status and has a link to the [https://treeherder.mozilla.org/perf.html#/graphs PerfHerder] | ||
* 13 pushes later, [http://hg.mozilla.org/graphs/file/tip/server/analysis/analyze_talos.py analyze_talos.py] is ran which compares your push to the previous 12 pushes and next 12 pushes to look for a [[ | * 13 pushes later, [http://hg.mozilla.org/graphs/file/tip/server/analysis/analyze_talos.py analyze_talos.py] is ran which compares your push to the previous 12 pushes and next 12 pushes to look for a [[/Talos/Data#Regressions|regression]] | ||
** if a regression is found, it will be posted on [https://treeherder.mozilla.org/perf.html#/alerts Perfherder Alerts] | ** if a regression is found, it will be posted on [https://treeherder.mozilla.org/perf.html#/alerts Perfherder Alerts] | ||
| Line 54: | Line 54: | ||
* http://ask.mozilla.org/question/45/how-can-i-know-if-my-push-to-try-regresses-talos-results/ | * http://ask.mozilla.org/question/45/how-can-i-know-if-my-push-to-try-regresses-talos-results/ | ||
* http://limpet.net/mbrubeck/2013/11/10/improving-regression-detection.html | * http://limpet.net/mbrubeck/2013/11/10/improving-regression-detection.html | ||
Revision as of 16:44, 6 August 2019
Talos
Talos is a Python performance testing framework that is usable on Windows, Mac and Linux. Talos is our versatile performance testing framework we use at Mozilla. It was created to serve as a test runner for the existing performance tests that Mozilla was running back in 2007 as well as providing an extensible framework for new tests as they were created.
So, why Talos? Talos is the bronze automaton of Greek myth. Talos protected the island of Crete, throwing giant boulders at unwary seamen. He's also purported to have heated himself glowing hot and then embraced his enemies. Basically, he was awesome.
Talos code lives at https://dxr.mozilla.org/mozilla-central/source/testing/talos
Talos Tests
Information about each test is available in tests
Running Talos Tests
See the page on running Talos tests.
Lifecycle of a Performance Test, from push to perfherder
- Taskcluster schedules talos jobs
- Taskcluster runs a talos job on a hardware machine when one is available - this is bootstrapped by Mozharness
- Mozharness\ downloads the build, talos.zip (found in [http://hg.mozilla.org/mozilla-central/tip/testing/talos/talos.json talos.json), and creates a virtualenv for running the test.
- Mozharness configures the test and runs it
- After the test is completed the data is uploaded to PerfHerder
- Treeherder displays a green (all OK) status and has a link to the PerfHerder
- 13 pushes later, analyze_talos.py is ran which compares your push to the previous 12 pushes and next 12 pushes to look for a regression
- if a regression is found, it will be posted on Perfherder Alerts
Resources / How-to
Adding a new test
To create a new test you ideally need a webpage(s) that performs the test(s) desired. The results can be a simple alert.
Once you've got that, just talk to folks in #perftest (:davehunt, :rwood, :igoldan) and they will handle the majority of the steps required.
Bugs
- Talos bugs are filed under Testing/Talos, such as requests for new tests or repairs to the talos code itself.
- Perfherder bugs are filed under [1].
- Talos machine maintenance bugs are filed under mozilla.org/Release Engineering, such as bugs having to do with the hardware that talos is run on or requests to run extra talos tests against a given build.
Subpages
- Definition of tests
- How to use Talos profiling.
- How to Run Talos, and how it is run in production.
- How to run Talos on mobile
- What our raw data looks like and what our formulas for filtering and summarization.
- History and other uses of Talos
Blog posts about Talos
- https://blog.mozilla.org/nfroyd/2012/09/19/looking-at-talos-differently/
- https://blog.mozilla.org/nfroyd/2012/10/05/looking-at-talos-differently-part-2/
- http://armenzg.blogspot.com/2011/12/taloszip-talosjson-and-you.html
- http://ask.mozilla.org/question/45/how-can-i-know-if-my-push-to-try-regresses-talos-results/
- http://limpet.net/mbrubeck/2013/11/10/improving-regression-detection.html