🚧 Firefox Performance Results 🚧

From MozillaWiki
Jump to: navigation, search

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

What do we have?


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

Query Tool

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



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.


[TODO] add description


Firefox Health

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

Firefox Performance Dashboard


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


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


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.


[TODO] add description


[TODO] add description


[TODO] add description


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.

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:

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.