3.3 Performance Pass
Last revised 13:00 CET March 29, 2007
Plan
- each team investigates its red performance tests and creates bugs with 'performance' keyword where needed
- the team lead prioritizes (see below) bugs that have the performance keyword and looks out for other performance related bugs
- the team lead prioritizes bugs reporting leaks (add the 'performance' keyword so that we find them easily). Here is a bug list with 'leak' in the summary.
- each team starts investigating and fixing their bugs according to assigned priority with the help of the performance team
Priorities
Those bugs we want to fix get a '3.3' or '3.3 M7' target milestone and the priority using the guidance below. The priority link
takes you to the list of the corresponding open 3.3 performance bugs.
- performance test degradations, especially when in the fingerprints
- bugs that slow down the user in most common scenarios, e.g. full build on startup
- leaks that happen in common scenarios and grow the memory each time
- bugs that obviously slow down the user
- all other leaks that grow each time the scenario is repeated
- other performance bugs that should be addressed for 3.3
- leaks that are not real leaks but holding on to last instance