Closed
Bug 1173772
Opened 11 years ago
Closed 10 years ago
Performance regression in Calendar
Categories
(Firefox OS Graveyard :: Gaia::Calendar, defect, P2)
Tracking
(blocking-b2g:2.5+)
RESOLVED
WORKSFORME
| blocking-b2g | 2.5+ |
People
(Reporter: raptor, Unassigned)
References
Details
(Keywords: perf, regression)
On Thu Jun 11 2015, Raptor detected a possible regression in Calendar:
Device: flame-kk
Memory: 319
Branch: master
Time: Tue Jun 09 2015 16:28:34 GMT+0000 (UTC)
---
Old Average: 1271.439ms
New Average: 1388.222ms
Regression: 116.78ms
Confidence level of this being legitimate regression: 8.36
---
Gaia revision: 23a22d32533f39d4
Previous Gaia revision: 956982413ef87c19
Gecko revision: 92120141e005
Previous Gecko revision: 92120141e005
---
Raptor URL: http://raptor.mozilla.org/#/dashboard/script/mark.js?device=flame-kk&branch=master&memory=319&suite=coldlaunch&to=1433953714000&from=1433780914000&panelId=1&fullscreen
Updated•11 years ago
|
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → DUPLICATE
Comment 2•11 years ago
|
||
Not sure how this is a duplicate. They have different times and different Gaia and Gecko revisions.
Status: RESOLVED → REOPENED
Resolution: DUPLICATE → ---
Comment 3•11 years ago
|
||
My mistake, Eli. Thanks. BTW, above Raptor URL is not working. Could you help to correct raptor URL generation?
Flags: needinfo?(eperelman)
Comment 4•11 years ago
|
||
Flags: needinfo?(eperelman)
Comment 5•11 years ago
|
||
Gareth, could you help to comment on this?
Updated•10 years ago
|
Priority: -- → P2
Updated•10 years ago
|
tracking-b2g:
+ → ---
Priority: P2 → P1
Comment 7•10 years ago
|
||
update new raptor link: https://raptor.mozilla.org/dashboard/script/measures?var-device=flame-kk&var-memory=319&var-branch=master&var-test=cold-launch&panelId=1&fullscreen
ni Dylan to get engineering team's help.
Priority: P1 → P2
Updated•10 years ago
|
Status: REOPENED → RESOLVED
Closed: 11 years ago → 10 years ago
Resolution: --- → WORKSFORME
Updated•10 years ago
|
Flags: needinfo?(gaye)
You need to log in
before you can comment on or make changes to this bug.
Description
•