Performance/Bugzilla: Difference between revisions
Jump to navigation
Jump to search
| (19 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
= Workflows = | = Workflows = | ||
* [[../Triage]] | * [[../Triage|Triage]] | ||
= Queries = | = Queries = | ||
* [ | * [[Performance/Triage#Queries|Triage]] | ||
= Reports = | = Reports = | ||
* [https://bugzilla.mozilla.org/report.cgi?x_axis_field= | * [https://bugzilla.mozilla.org/report.cgi?x_axis_field=cf_performance_impact&y_axis_field=component&query_format=report-table&resolution=---&j_top=AND&f1=cf_performance_impact&o1=isnotempty&v1=&f2=cf_performance_impact&o2=nowordssubstr&v2=-%2C%3F&format=table&action=wrap Performance Impact × Component] | ||
* [https://bugzilla.mozilla.org/report.cgi?x_axis_field= | * [https://bugzilla.mozilla.org/report.cgi?x_axis_field=cf_performance_impact&y_axis_field=priority&query_format=report-table&resolution=---&j_top=AND&f1=cf_performance_impact&o1=isnotempty&v1=&f2=cf_performance_impact&o2=nowordssubstr&v2=-%2C%3F&format=table&action=wrap Performance Impact × Priority] | ||
* [https://bugzilla.mozilla.org/report.cgi?x_axis_field=cf_performance_impact&y_axis_field=bug_severity&query_format=report-table&resolution=---&j_top=AND&f1=cf_performance_impact&o1=isnotempty&v1=&f2=cf_performance_impact&o2=nowordssubstr&v2=-%2C%3F&format=table&action=wrap Performance Impact × Severity] | |||
* [https://mozilla.pettay.fi/performance.html Performance × Component, including deltas over 30 days] | |||
= Project Flag = | = Project Flag = | ||
We have a '''Performance''' project flag used for triage nomination and prioritisation. Anyone can nominate bugs for triage, but only members of the [[#Groups|perf-triage-team group]] can prioritise or mark bugs as unrelated to performance. | We have a '''Performance Impact''' project flag used for triage nomination and prioritisation. Anyone can (re)nominate bugs for triage, but only members of the [[#Groups|perf-triage-team group]] can prioritise or mark bugs as unrelated to performance. | ||
{| class="wikitable" | |||
|- | |||
! Value !! Description | |||
|- | |||
| [https://bugzilla.mozilla.org/buglist.cgi?f1=cf_performance_impact&o1=equals&v1=%3F&resolution=---&query_format=advanced ?] || Add bug to triage queue. | |||
|- | |||
| [https://bugzilla.mozilla.org/buglist.cgi?f1=cf_performance_impact&o1=equals&v1=none&resolution=---&query_format=advanced none] || Bug has no impact on product performance. | |||
|- | |||
| [https://bugzilla.mozilla.org/buglist.cgi?f1=cf_performance_impact&o1=equals&v1=high&resolution=---&query_format=advanced high] || Bug has a high impact on the product quality and experience. These bugs should ideally be resolved within 3-6 months. | |||
|- | |||
| [https://bugzilla.mozilla.org/buglist.cgi?f1=cf_performance_impact&o1=equals&v1=medium&resolution=---&query_format=advanced medium] || Bug has a noticeable impact for a number of users. These bugs should ideally be resolved within 6-12 months. | |||
|- | |||
| [https://bugzilla.mozilla.org/buglist.cgi?f1=cf_performance_impact&o1=equals&v1=low&resolution=---&query_format=advanced low] || Bug has a noticeable performance impact but affects a group of users small enough, or the impact is low enough that it should be resolved in accordance with other priorities. | |||
|- | |||
| [https://bugzilla.mozilla.org/buglist.cgi?f1=cf_performance_impact&o1=equals&v1=pending-needinfo&resolution=---&query_format=advanced pending-needinfo] || Bug is waiting on further information before impact can be determined. | |||
|} | |||
= Keywords = | = Keywords = | ||
* '''perf''' | * '''{{BugzillaKeyword|perf}}''' A bug that affects speed or responsiveness. (For memory use issues, use "memory-footprint" or "memory-leak" instead.) | ||
* '''perf-alert''' | * '''{{BugzillaKeyword|perf-alert}}''' Associated with a performance alert. | ||
* '''perf:responsiveness''' | * '''{{BugzillaKeyword|perf:responsiveness}}''' The issue affects the promptness of the browser’s response to user input. | ||
* '''perf:resource-use''' | * '''{{BugzillaKeyword|perf:resource-use}}''' The issue affects resource use excessively: cpu, gpu, ram, disk access, power, etc. | ||
* '''perf:pageload''' | * '''{{BugzillaKeyword|perf:pageload}}''' The issue affects the initial loading of websites. | ||
* '''perf:frontend''' | * '''{{BugzillaKeyword|perf:frontend}}''' The issue affects the browser front-end (i.e. the Firefox UI.) | ||
* '''perf:animation''' | * '''{{BugzillaKeyword|perf:animation}}''' The issue affects the smoothness of animations. | ||
* '''perf:startup''' | * '''{{BugzillaKeyword|perf:startup}}''' The issue affects application startup. | ||
= Groups = | = Groups = | ||
* [https://bugzilla.mozilla.org/page.cgi?id=group_members.html&group=perf-triage-team perf-triage-team] | * [https://bugzilla.mozilla.org/page.cgi?id=group_members.html&group=perf-triage-team perf-triage-team] | ||
Latest revision as of 11:42, 4 December 2023
Workflows
Queries
Reports
- Performance Impact × Component
- Performance Impact × Priority
- Performance Impact × Severity
- Performance × Component, including deltas over 30 days
Project Flag
We have a Performance Impact project flag used for triage nomination and prioritisation. Anyone can (re)nominate bugs for triage, but only members of the perf-triage-team group can prioritise or mark bugs as unrelated to performance.
| Value | Description |
|---|---|
| ? | Add bug to triage queue. |
| none | Bug has no impact on product performance. |
| high | Bug has a high impact on the product quality and experience. These bugs should ideally be resolved within 3-6 months. |
| medium | Bug has a noticeable impact for a number of users. These bugs should ideally be resolved within 6-12 months. |
| low | Bug has a noticeable performance impact but affects a group of users small enough, or the impact is low enough that it should be resolved in accordance with other priorities. |
| pending-needinfo | Bug is waiting on further information before impact can be determined. |
Keywords
- perf A bug that affects speed or responsiveness. (For memory use issues, use "memory-footprint" or "memory-leak" instead.)
- perf-alert Associated with a performance alert.
- perf:responsiveness The issue affects the promptness of the browser’s response to user input.
- perf:resource-use The issue affects resource use excessively: cpu, gpu, ram, disk access, power, etc.
- perf:pageload The issue affects the initial loading of websites.
- perf:frontend The issue affects the browser front-end (i.e. the Firefox UI.)
- perf:animation The issue affects the smoothness of animations.
- perf:startup The issue affects application startup.