Difference between revisions of "Firefox Performance Testing Lab Fall 2010"
Cadecairos (talk | contribs) (→Bug Reports) |
(→Bug Reports) |
||
| Line 67: | Line 67: | ||
'''NOTE:''' All bugs related to what we find should have '''[chromeexperiments]''' in the bug's Whiteboard field, so we can track them. The following Bugzilla search will list them all: <nowiki>https://bugzilla.mozilla.org/buglist.cgi?quicksearch=[chromeexperiments]</nowiki> | '''NOTE:''' All bugs related to what we find should have '''[chromeexperiments]''' in the bug's Whiteboard field, so we can track them. The following Bugzilla search will list them all: <nowiki>https://bugzilla.mozilla.org/buglist.cgi?quicksearch=[chromeexperiments]</nowiki> | ||
| − | *[https://bugzilla.mozilla.org/show_bug.cgi?id=596677 Sand Trap bug(dupe)] | + | * [https://bugzilla.mozilla.org/show_bug.cgi?id=596677 Sand Trap bug(dupe)] |
| − | *[https://bugzilla.mozilla.org/show_bug.cgi?id=595963 Open Sand Trap bug] | + | * [https://bugzilla.mozilla.org/show_bug.cgi?id=595963 Open Sand Trap bug] |
| − | *[https://bugzilla.mozilla.org/show_bug.cgi?id=596707 Sand Trap graphics bug] | + | * [https://bugzilla.mozilla.org/show_bug.cgi?id=596707 Sand Trap graphics bug] |
| + | * [https://bugzilla.mozilla.org/show_bug.cgi?id=596746 Sand Trap painting perf bug] | ||
Revision as of 16:43, 15 September 2010
Contents
Goal
The goal of this lab is twofold. First, to provide students with a real-world experience of working collaboratively in an open community; and second, to work on a cutting-edge, but manageable project within the Mozilla community.
Objective
To conduct A/B performance tests of the Chrome Experiments using nightly builds of both Firefox and Chrome, in order to identify performance bottlenecks in Firefox. Also, to profile and file bugs in order to fix these issues.
Method
- As a group determine a method for dividing the Chrome Experiments so they all get tested
- Install both the Firefox and Chrome nightly builds
- Test each experiment in the two browsers, looking for various issues:
- Speed - is Firefox as fast as Chrome at rendering the graphics?
- Smoothness - are the graphics as smooth as in Chrome? Do you notice a lot of pauses, jerkiness, etc.?
- Responsiveness - does Firefox remain responsive while you run the demo? Is it pegging your CPU(s)?
- Record your findings, as well as browser and computer info ([about:support], [about:]) in the Results Spreadsheet.
Resources
- Chrome Experiments
- Results Spreadsheet. Talk to Dave to get permissions in order to edit.
- Firefox (i.e., Minefield) nightly builds
- Chrome (i.e., Chromium) nightly builds
- Example performance bug
Tests
(humph) Let's refine this a bit more, such that we track:
Name of Experiment | URL of Experiment | Your Name | Date of Test | Hardware Info | Browser Info | Firefox Performance - Speed | Firefox Performance - Smoothness | Firefox Performance - Responsiveness | Notes and other Details |
(carl) Separate or cumulative results page?
| Test No. | Name |
Results |
|---|---|---|
| 1-10 | Carl | Result |
| 11-20 | Kevin Lasconia | - |
| 21-30 | - | - |
| 31-40 | Stephen Bologna | - |
| 41-50 | - | - |
| 51-60 | - | - |
| 61-70 | Brian Law | Result |
| 71-80 | Steven | - |
| 81-90 | - | - |
| 91-100 | - | - |
| 101-110 | Crystal de Nobrega | - |
| 111-120 | Chris DeCairos | Result |
Bug Reports
NOTE: All bugs related to what we find should have [chromeexperiments] in the bug's Whiteboard field, so we can track them. The following Bugzilla search will list them all: https://bugzilla.mozilla.org/buglist.cgi?quicksearch=[chromeexperiments]
