TestEngineering/Performance/Results: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
No edit summary
 
(15 intermediate revisions by the same user not shown)
Line 1: Line 1:
{{DISPLAYTITLE:Firefox Performance Results}}
{{DISPLAYTITLE:Firefox 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.
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? =
= What should I use? =
{{todo|for now just gathering ideas}}
* Does my patch affect performance?
* Does my patch affect performance?
** [[#Compare|Perfherder compare]]
* Did my push affect performance?
* Did my push affect performance?
** [[#Compare|Perfherder compare]]
* How does Firefox compare against other browsers?
* How does Firefox compare against other browsers?
** [[#Firefox Performance Dashboard|Firefox Performance Dashboard]]
* Are we meeting our goals?
* Are we meeting our goals?
* What performance tests are we running?
* What performance tests are we running?
* What platforms are we running performance tests against?
* What platforms are we running performance tests against?


= Data Sources =
= What do we have? =
== ActiveData Query Tool ==
ActiveData is a collection of billions of records covering unit tests, jobs, performance data, and source code revision history. The intended use 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
* Access: Public
* Audience: Engineers
* Documentation: [[EngineeringProductivity/Projects/ActiveData]]
* Source code: https://github.com/mozilla/activedata
* Issue tracker: https://bugzilla.mozilla.org/buglist.cgi?product=Testing&component=ActiveData&resolution=---
* Contact: Kyle Lahnakoski [ekyle]
 
=== Examples ===
* [https://activedata.allizom.org/tools/query.html#query_id=rqnxuVpf Performance frameworks]
* [https://activedata.allizom.org/tools/query.html#query_id=rqnxuVpf Performance suites]
* [https://activedata.allizom.org/tools/query.html#query_id=1dtPBeZR Performance suites running on Android hardware]
 
== ActiveData 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/
* Access: Public
* 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 [https://bugzilla.mozilla.org/enter_bug.cgi?assigned_to=nobody%40mozilla.org&bug_ignored=0&bug_severity=normal&bug_status=NEW&bug_type=task&cf_fx_iteration=---&cf_fx_points=---&cf_status_firefox68=---&cf_status_firefox69=---&cf_status_firefox70=---&cf_status_firefox_esr60=---&cf_status_firefox_esr68=---&cf_tracking_firefox68=---&cf_tracking_firefox69=---&cf_tracking_firefox70=---&cf_tracking_firefox_esr60=---&cf_tracking_firefox_esr68=---&cf_tracking_firefox_relnote=---&comment=Please%20add%20%5Bemail%5D%20to%20the%20cloudservices_datadog%20LDAP%20group%20and%20be%20sent%20an%20invitation%20to%20access%20Datadog%3F&component=Operations&contenttypemethod=list&contenttypeselection=text%2Fplain&defined_groups=1&flag_type-37=X&flag_type-607=X&flag_type-708=X&flag_type-721=X&flag_type-737=X&flag_type-748=X&flag_type-787=X&flag_type-800=X&flag_type-803=X&flag_type-846=X&flag_type-864=X&flag_type-929=X&flag_type-936=X&flag_type-941=X&form_name=enter_bug&maketemplate=Remember%20values%20as%20bookmarkable%20template&op_sys=Unspecified&priority=--&product=Cloud%20Services&rep_platform=Unspecified&short_desc=Grant%20%5Buser%5D%20access%20to%20Datadog&target_milestone=---&version=unspecified 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.
 
* 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
* Contact: Kyle Lahnakoski [ekyle]


== Firefox Performance Dashboard ==
== Firefox Performance Dashboard ==
* Location: https://arewefastyet.com/  
* Location: https://arewefastyet.com/  
* Access: Public
* Access: Public
* Audience: Managers
* Audience: Managers, Engineers
* Documentation: {{todo|add link to documentation}}
* Documentation: {{todo|add link to documentation}}
* Source code: https://github.com/mozilla-frontend-infra/firefox-performance-dashboard
* Source code: https://github.com/mozilla-frontend-infra/firefox-performance-dashboard
* Issue tracker: https://github.com/mozilla-frontend-infra/firefox-performance-dashboard/issues
* Issue tracker: https://github.com/mozilla-frontend-infra/firefox-performance-dashboard/issues
* Contact: Armen Zambrano Gasparnian [armenzg]
* Contact: Dave Hunt [davehunt]


== Metrics ==
== Metrics ==
{{todo|https://metrics.mozilla.com/protected/shiny/cdowhygelund/firefox-perf-telemetry-dashboard/}}
{{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 ==
Line 113: Line 57:
* Documentation: {{todo|}}
* Documentation: {{todo|}}


== Redash ==
== STMO ==
{{todo|add description}}
STMO is shorthand for [https://sql.telemetry.mozilla.org/ sql.telemetry.mozilla.org], an installation of the excellent [https://redash.io/ 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/
* Location: https://sql.telemetry.mozilla.org/
* Access: {{todo|}}
* Access: LDAP via SSO
* Audience: Sheriffs, Engineers, Managers
* Audience: Sheriffs, Engineers, Managers
* Documentation: {{todo|}}
* Documentation: https://docs.telemetry.mozilla.org/tools/stmo.html
* Source code: {{todo|}}
* Source code: https://github.com/mozilla/redash
* Issue tracker: {{todo|}}
* Issue tracker: https://github.com/mozilla/redash/issues
* Contact: {{todo|}}
* Contact: #fx-metrics on Slack


== Ad-hoc results ==
== Ad-hoc results ==
{{todo|add description}}
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:


* [https://drive.google.com/drive/u/0/folders/1sZ6C6bku2vR575GSH5DxgSlP43JYT-Je Performance/Results]
* [https://drive.google.com/drive/folders/11a90GH_xwcqwkcAmzCZAkwmQeuSoXA3n Performance/Projects/Desktop/Testing]
* [https://drive.google.com/drive/folders/11a90GH_xwcqwkcAmzCZAkwmQeuSoXA3n 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.

Latest revision as of 16:17, 11 August 2021

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?

Firefox Performance Dashboard

Metrics

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

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.

Alerts

[TODO] add description

Compare

[TODO] add description

Graphs

[TODO] add description

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.

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.

Retrieved from "https://wiki.allizom.org/index.php?title=TestEngineering/Performance/Results&oldid=1237229"