Closed Bug 951221 Opened 11 years ago Closed 11 years ago

[1.3] Settings app scroll latency

Categories

(Firefox OS Graveyard :: Gaia::Settings, defect, P1)

ARM
Gonk (Firefox OS)
defect

Tracking

(blocking-b2g:1.3+)

RESOLVED WORKSFORME
1.3 C3/1.4 S3(31jan)
blocking-b2g 1.3+

People

(Reporter: mvikram, Assigned: mchang)

References

Details

(Keywords: perf, Whiteboard: [c=handeye p=4 s= u=1.3])

Attachments

(1 file, 1 obsolete file)

On the Settings app, we notice stutters while scrolling. On a multi-core device with faster CPUs/GPU, the janks should be minimal. On more capable devices, the scroll fps should be 60 and these janks affect it.
blocking-b2g: --- → 1.3?
OS: Windows 7 → Gonk (Firefox OS)
Hardware: x86_64 → ARM
Please also refer to: https://bugzilla.mozilla.org/show_bug.cgi?id=856708. Scrolling issues relate more to (1) and (2).
Triage: we would need specific info to determine blocking status. (In reply to Mandyam Vikram from comment #0) > On the Settings app, we notice stutters while scrolling. On a multi-core > device with faster CPUs/GPU, the janks should be minimal. On more capable > devices, the scroll fps should be 60 and these janks affect it. Are you referring to general scrolling or scrolling right after cold launch? For the former APZ is already scheduled to be enabled on 1.3; for latter unless the experience regressed there isn't really nothing to fix.
In reply to https://bugzilla.mozilla.org/show_bug.cgi?id=951221#c2: > Are you referring to general scrolling or scrolling right after cold launch? For the former APZ is already > scheduled to be enabled on 1.3; for latter unless the experience regressed there isn't really nothing to > > fix. Can you please clarify the difference of cold launch versus general scrolling? Do you mean launching the app for the first time after it has booted? Can you also explain why APZC would not help in both cold launch and general scrolling?
Can you also please point me to the Bugzilla regarding turning on AZPC for 1.3?
(In reply to Mandyam Vikram from comment #3) > In reply to https://bugzilla.mozilla.org/show_bug.cgi?id=951221#c2: > > > Are you referring to general scrolling or scrolling right after cold launch? For the former APZ is already > > scheduled to be enabled on 1.3; for latter unless the experience regressed there isn't really nothing to > > fix. > > Can you please clarify the difference of cold launch versus general > scrolling? Do you mean launching the app for the first time after it has > booted? Yes. (In reply to Mandyam Vikram from comment #4) > Can you also please point me to the Bugzilla regarding turning on AZPC for > 1.3? bug 909877.
Keywords: perf
blocking-b2g: 1.3? → 1.3+
Whiteboard: [c=handeye p= s= u=1.3]
Assignee: nobody → mchang
Status: NEW → ASSIGNED
Whiteboard: [c=handeye p= s= u=1.3] → [c=handeye p=4 s= u=1.3]
Depends on: 950250
Priority: -- → P1
Attached file Profile of Scrolling With Settings App (obsolete) (deleted) —
Looks like we have very long rasterize times, much larger than our allotted 16 ms Render Times, which causes us to jank / lose frames.
Attached file Updated Profile of Settings App (deleted) —
Attachment #8357443 - Attachment is obsolete: true
Depends on: 957886
Depends on: 957913
Depends on: 958318
Mason, Next steps to getting this blocker fixed?
Flags: needinfo?(mchang)
Finish the dependent bugs, which should help with performance here. Hopefully we will be able to close without bug 957886.
Flags: needinfo?(mchang)
I'm hoping fixing bug 950250 and 958318 will be enough to close this out.
Landed bug 958318 in both gaia and uplifted to v1.3. Vikram, can you please retest to see if it improved? Thanks!
Flags: needinfo?(mvikram)
PM triaged this bug and it should remain a 1.3 blocker.
Will have results early this week.
Flags: needinfo?(mvikram)
Target Milestone: --- → 1.3 C3/1.4 S3(31jan)
From testing results on the following recent build, the FPS was measured as close to 60 FPS. Gecko: dbb70aeb55524a3513a3c4d10cd8a8e424589a99 Gaia: 50d6487d4d15efda942c934570e6fdfb91f6fe2e Setting this as worksforme.
Status: ASSIGNED → RESOLVED
Closed: 11 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: