Performance/Triage: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
No edit summary
No edit summary
Line 32: Line 32:


Sometimes the information isn't enough to make a decision, in that case we can "need info" the reporter asking for more data, for example an export of `about:support` or a performance profile, or simply more information about the steps to reproduce.
Sometimes the information isn't enough to make a decision, in that case we can "need info" the reporter asking for more data, for example an export of `about:support` or a performance profile, or simply more information about the steps to reproduce.
= Templates =
== New bug ==
This template is included in the description for new bugs opened in the Core::Performance component. If a bug is opened in another component and then moved to Core::Performance, this template can be used as needed to request additional information from the reporter.
<pre>
### Basic information
Steps to Reproduce:
Expected Results:
Actual Results:
---
### Performance recording (profile)
Profile URL:
(If this report is about slow performance or high CPU usage, please capture a performance profile by following the instructions at https://profiler.firefox.com/. Then upload the profile and insert the link here.)
#### System configuration:
OS version:
GPU model:
Number of cores:
Amount of memory (RAM):
### More information
Please consider attaching the following information after filing this bug, if relevant:
- Screenshot / screen recording
- Anonymized about:memory dump, for issues with memory usage
- Troubleshooting information: Go to about:support, click "Copy text to clipboard", paste it to a file, save it, and attach the file here.
---
Thanks so much for your help.
</pre>
== No longer able to reproduce ==
<pre>This bug doesn’t seem to happen anymore in current versions of Firefox. Please reopen or file a new bug if you see it again.</pre>
== No response from reporter ==
<pre>With no answer from the reporter, we don’t have enough data to reproduce and/or fix this issue. Please reopen or file a new bug with more information if you see it again.</pre>
== Expected behaviour ==
<pre>This is expected behavior. Please reopen or file a new bug if you think otherwise.</pre>
== Website issue ==
<pre>According to the investigation, this is a website issue. Please reopen or file a new bug if you think otherwise.</pre>

Revision as of 15:40, 31 March 2022


Queries

  1. Triage nominations and Core::Performance without priority
  2. Triage nominations and Core::Performance without priority (pending needinfo)
  3. Recently opened bugs with performance keywords in the summary

Resources

Nomination

To nominate a bug for triage, set the Performance flag in Bugzilla to ?

This can be found by clicking Show Advanced Fields followed by Set bug flags when entering a new bug:

Bugzilla performance nomination on new bug form.png

Or by expanding the Tracking section when editing an existing bug:

Screenshot 2022-02-24 at 19.53.54.png

Triage Process

The goals of the triage process are:

  • determine if the bug is a performance issue
  • assign a priority using the performance flag
  • assign appropriate keywords
  • move the bug to the most suitable component

The calculator is a good way to find the right priority.

Sometimes the information isn't enough to make a decision, in that case we can "need info" the reporter asking for more data, for example an export of `about:support` or a performance profile, or simply more information about the steps to reproduce.

Templates

New bug

This template is included in the description for new bugs opened in the Core::Performance component. If a bug is opened in another component and then moved to Core::Performance, this template can be used as needed to request additional information from the reporter.

### Basic information

Steps to Reproduce:


Expected Results:


Actual Results:


---

### Performance recording (profile)

Profile URL:
(If this report is about slow performance or high CPU usage, please capture a performance profile by following the instructions at https://profiler.firefox.com/. Then upload the profile and insert the link here.)

#### System configuration:

OS version:
GPU model:
Number of cores: 
Amount of memory (RAM): 

### More information

Please consider attaching the following information after filing this bug, if relevant:

 - Screenshot / screen recording
 - Anonymized about:memory dump, for issues with memory usage
 - Troubleshooting information: Go to about:support, click "Copy text to clipboard", paste it to a file, save it, and attach the file here.

---

Thanks so much for your help.

No longer able to reproduce

This bug doesn’t seem to happen anymore in current versions of Firefox. Please reopen or file a new bug if you see it again.

No response from reporter

With no answer from the reporter, we don’t have enough data to reproduce and/or fix this issue. Please reopen or file a new bug with more information if you see it again.

Expected behaviour

This is expected behavior. Please reopen or file a new bug if you think otherwise.

Website issue

According to the investigation, this is a website issue. Please reopen or file a new bug if you think otherwise.