Closed Bug 942242 Opened 11 years ago Closed 11 years ago

email FPS regressed on v1.2 (from earlier v1.2)

Categories

(Firefox OS Graveyard :: Gaia::E-Mail, defect, P1)

ARM
Gonk (Firefox OS)
defect

Tracking

(blocking-b2g:-, b2g-v1.2 affected)

RESOLVED WORKSFORME
blocking-b2g -
Tracking Status
b2g-v1.2 --- affected

People

(Reporter: bkelly, Assigned: bkelly)

References

Details

(Keywords: perf, regression, Whiteboard: [c=handeye p=5 s= u=1.2])

Breaking out the email fps issue from the parent meta bug 936535.

(In reply to Mandyam Vikram from comment #9)
> We are observing something similar as well. Please treat the following
> results as not final (testing in progress).
> We are observing FPS numbers of ~37 fps for the following build:
> Gecko:
> 964f7c844f2793092bab72612d5da2f5bcfd6c2e
> Gaia:
> be4ea00a50236b10eb0a03232a28ffd0048e0cb8
Based on high speed camera measurements on the following from the build this week on the high speed camera, the measurements have improved to 53 fps:
Gecko:
14432474328e7558902329c3fc2a8238c3222a7f
Gaia:
7a23f8c53ba97da9c63a7275b36d155b4526a639

Seems like this regression has been resolved.
I see noticeable jank scroll email at the moment.  It appears related to bug 932418.  I think we should try to get that fixed and uplifted if we can.
Depends on: 943498
Vikram, I discussed this with mlee and I believe we decided to go ahead and mark this fixed based on comment 1.  We are still working on the dependent bugs here, but we don't want to rush them for 1.2 is current performance is acceptable.  Please let me know if this is an issue.  Thanks!
Status: ASSIGNED → RESOLVED
Closed: 11 years ago
Resolution: --- → WORKSFORME
blocking-b2g: koi? → -
Marking it as Resolved is ok. Is the plan to being in the dependent bugs in 1.2 or 1.3? If the risk is minimal, we can target 1.2 as we do see a fair amount of stutters.
At this point I think removing the email scroll jank will be risky to uplift.  My investigation in bug 943498 has not revealed any immediate fix and may require refactoring the DOM, etc.  Therefore I recommend any solution to this problem ride the trains and go into 1.3.
That being said, we might be able to uplift the changes to bug 932418.  It removes some jank and I believe it is fairly safe.  If you would like us to uplift that, can you comment on that bug?  Thanks.
You need to log in before you can comment on or make changes to this bug.