Closed
Bug 915241
Opened 11 years ago
Closed 11 years ago
[1.2] Regression in Gallery Scroll FPS (compared to [1.1])
Categories
(Firefox OS Graveyard :: Gaia::Gallery, defect, P1)
Tracking
(blocking-b2g:koi+, b2g-v1.2 fixed)
People
(Reporter: mvikram, Assigned: jhylands)
References
Details
(Keywords: perf, regression, Whiteboard: [c=handeye p= s= u=1.2] )
User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/29.0.1547.66 Safari/537.36
Steps to reproduce:
Based on high speed camera measurements (on a QRD 7x27 device), there seems to be a degradation in UX scroll performance of the Gallery App.
Actual results:
Measurements on 1.2:
51 FPS
Measurements on 1.1:
58 FPS
Reporter | ||
Updated•11 years ago
|
Severity: normal → blocker
blocking-b2g: --- → koi?
Depends on: 915239
OS: All → Gonk (Firefox OS)
Priority: -- → P1
Updated•11 years ago
|
blocking-b2g: koi? → koi+
Keywords: regression
Comment 2•11 years ago
|
||
Per Sandip in bug 915239: Minimum Expected Benchmark for Gallery App Scrolling is 55 FPS.
Comment 3•11 years ago
|
||
Recent preliminary QA testing on Leo was showing 42-56fps, so we may be in range, and we need to do it on the right device and with the same methodology to be sure.
Updated•11 years ago
|
Assignee: nobody → jhylands
Assignee | ||
Comment 4•11 years ago
|
||
Milan, do we have a definitive answer on this? The dependent bugs have been marked resolved.
Flags: needinfo?(milan)
Comment 5•11 years ago
|
||
We are waiting for QC to confirm. They are currently the ones that can measure using the same methodology as for 1.1, so we need them to come back with the latest results.
Flags: needinfo?(milan)
Assignee | ||
Comment 6•11 years ago
|
||
Per Qualcomm's report, scroll performance has increased from 51 to 57 FPS, which is in line with 1.1 numbers, so I am closing this bug as fixed.
Status: UNCONFIRMED → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Updated•11 years ago
|
status-b2g-v1.2:
--- → fixed
You need to log in
before you can comment on or make changes to this bug.
Description
•