TestEngineering/Performance/Results

There are a variety of places where performance results are available, some of these can be queried directly, and others are dashboards built on top of those sources.

What should I use?

[TODO] for now just gathering ideas

• Does my patch affect performance?
  • Perfherder compare
• Did my push affect performance?
  • Perfherder compare
• How does Firefox compare against other browsers?
  • Firefox Health
  • Firefox Performance Dashboard
• Are we meeting our goals?
  • Firefox Health
• What performance tests are we running?
  • ActiveData
• What platforms are we running performance tests against?
  • ActiveData

What do we have?

ActiveData

ActiveData is a collection of billions of records covering unit tests, jobs, performance data, and source code revision history.

• Access: Public
• Audience: Engineers
• Documentation: EngineeringProductivity/Projects/ActiveData
• Issue tracker: https://bugzilla.mozilla.org/buglist.cgi?product=Testing&component=ActiveData&resolution=---
• Contact: Kyle Lahnakoski [ekyle]

Query Tool

The intended use for ActiveData is for automated clients or for building dashboards, however the query tool can be used for exploration.

• Location: https://activedata.allizom.org/tools/query.html
• Source code: https://github.com/mozilla/activedata

Examples

• Performance frameworks
• Performance suites
• Performance suites running on Android hardware

Recipes

Due to the size and complexity of ActiveData, using it to answer everyday questions is not a straightforward task and the built-in query tool is often insufficient. ActiveData Recipes was created to provide an intuitive way to not only use ActiveData, but to save your queries for future use and share them with others.

• Location: https://adr-dev.herokuapp.com/
• Audience: Engineers, Managers
• Documentation: https://active-data-recipes.readthedocs.io/
• Source code: https://github.com/mozilla/active-data-recipes
• Issue tracker: https://github.com/mozilla/active-data-recipes/issues
• Contact: Andrew Halberstadt [ahal]

Datadog

[TODO] add description

WebPageTest

• Location: https://app.datadoghq.com/dashboard/lists/manual/18187
• Access: File a bug to request access by replacing [user] and [email] in this template.
• Audience: Engineers, Managers
• Documentation: https://mozilla-wpt-api-docs.readthedocs.io/
  [TODO] add doc on how to use datadog
• Source code: https://github.com/mozilla/wpt-api
• Issue tracker: https://github.com/mozilla/wpt-api/issues
• Contact: Stephen Donner [stephend]

Firefox Health

The health dashboard tracks metrics and statistics important for tracking performance improvements.

Warning: The Firefox Health dashboard does not currently have an owner. If you are experiencing issues with this dashboard please contact Dave Hunt [:davehunt] or Sarah Clements [:sclements]. If your issue is urgent please file a bug

.

• Location: https://health.graphics/
• Access: Public
• Audience: Managers
• Documentation:
  [TODO] add link to documentation
• Source code: https://github.com/mozilla-frontend-infra/firefox-health-dashboard
• Issue tracker: https://github.com/mozilla-frontend-infra/firefox-health-dashboard/issues

Firefox Performance Dashboard

• Location: https://arewefastyet.com/
• Access: Public
• Audience: Managers
• Documentation:
  [TODO] add link to documentation
• Source code: https://github.com/mozilla-frontend-infra/firefox-performance-dashboard
• Issue tracker: https://github.com/mozilla-frontend-infra/firefox-performance-dashboard/issues
• Contact: Armen Zambrano Gasparnian [armenzg]

Metrics

[TODO] https://metrics.mozilla.com/protected/shiny/cdowhygelund/firefox-perf-telemetry-dashboard/

Nimbledroid

[TODO] add description

• Location: https://nimbledroid.com/my_apps
• Access: Private
  [TODO] add details
• Audience: Engineers
• Documentation:
  [TODO] add link to documentation
• Issue tracker:
  [TODO]
• Contact: No-Jun Park [npark]

Perfherder

Perfherder is an interactive dashboard intended to allow monitoring and analysis of automated performance tests run against Mozilla products. Perfherder is part of the Treeherder project.

• Location: https://treeherder.mozilla.org/perf.html
• Access: Public
• Audience: Sheriffs, Engineers
• Documentation: EngineeringProductivity/Projects/Perfherder
• Source code: https://github.com/mozilla/treeherder
• Issue tracker: https://bugzilla.mozilla.org/buglist.cgi?product=Tree%20Management&component=Perfherder&resolution=---
• Contact: Sarah Clements [sclements]

Alerts

[TODO] add description

• Location: https://treeherder.mozilla.org/perf.html#/alerts
• Documentation:
  [TODO]

Compare

[TODO] add description

• Location: https://treeherder.mozilla.org/perf.html#/comparechooser
• Documentation:
  [TODO]

Graphs

[TODO] add description

• Location: https://treeherder.mozilla.org/perf.html#/graphs
• Documentation:
  [TODO]

STMO

STMO is shorthand for sql.telemetry.mozilla.org, an installation of the excellent Re:dash data analysis and dashboarding tool that has been customized and configured for use with a number of the Firefox organisation's data sets.

• Location: https://sql.telemetry.mozilla.org/
• Access: LDAP via SSO
• Audience: Sheriffs, Engineers, Managers
• Documentation: https://docs.telemetry.mozilla.org/tools/stmo.html
• Source code: https://github.com/mozilla/redash
• Issue tracker: https://github.com/mozilla/redash/issues
• Contact: #fx-metrics on Slack

Ad-hoc results

Before performance tests are fully automated and integrated into our pipeline, we often run manual or semi-automated tests. These results are often presented in ways that don't fit into our existing reporting structures, such as spreadsheets or documents. The following list of links serves as a repository for these results:

• Performance/Results
• Performance/Projects/Desktop/Testing

Please make sure when you add results to the above locations that the name or internal labeling is clear as to what was tested, the methods used, when the results were gathered, and anything else that may be useful.