Closed
Bug 689578
Opened 13 years ago
Closed 13 years ago
Talos regressions on Android and Maemo [09/24]
Categories
(Firefox for Android Graveyard :: General, defect)
Tracking
(Not tracked)
VERIFIED
FIXED
Firefox 9
People
(Reporter: mfinkle, Assigned: mfinkle)
References
Details
(Keywords: perf, regression, Whiteboard: [QA!])
Attachments
(1 file)
|
44.24 KB,
patch
|
mbrubeck
:
review+
|
Details | Diff | Splinter Review |
Several metrics regressed when a mozilla-inbound merge happened on 09/24. Example:
Regression Tp4 increase 54% on Nokia n900 mobile
---------------------------------------------------
Previous: avg 8025.026 stddev 58.521 of 30 runs up to revision fecae145d884
New : avg 12362.240 stddev 84.480 of 5 runs since revision f08484868187
Change : +4337.214 (54% / z=74.113)
Graph : http://mzl.la/pFmFov
Changeset range: http://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=fecae145d884&tochange=f08484868187
We have no Android Tp data from this time period (bug 689350)
We thought it was bug 683802, but that bug has since been acquitted.
It looks like it could be bug 688689, so this patch reverts back to the old throbber. I also revert a bit of bug 688677, changing back to 32px favicons.
Attachment #562769 -
Flags: review?(mbrubeck)
|
||
Updated•13 years ago
|
Attachment #562769 -
Flags: review?(mbrubeck) → review+
|
||
Comment 1•13 years ago
|
||
As a sidenote, here is the Firefox desktop version of this bug.
|
|
||
Comment 2•13 years ago
|
||
Fixed by backout of bug 688689.
Assignee: nobody → mark.finkle
Blocks: 688689
Status: NEW → RESOLVED
Closed: 13 years ago
Keywords: perf,
regression
OS: Linux → Maemo
Hardware: x86 → ARM
Resolution: --- → FIXED
|
|
||
Comment 3•13 years ago
|
||
http://hg.mozilla.org/mozilla-central/rev/115e3576acf5
Target Milestone: --- → Firefox 9
|
||
Updated•13 years ago
|
Whiteboard: QA?
|
||
Comment 4•13 years ago
|
||
Verified by inspection of http://graphs.mozilla.org link from comment 0 set to 30 days.
Status: RESOLVED → VERIFIED
Whiteboard: QA? → [QA!]
You need to log in
before you can comment on or make changes to this bug.
Description
•