[meta] Contact app launch latency is worse compared to Android on quad core 1 GB device



5 years ago
4 years ago


(Reporter: tkundu, Assigned: bobby.chien+bugzilla)



Gonk (Firefox OS)
Dependency tree / graph
Bug Flags:
in-moztrap -

Firefox Tracking Flags



(Whiteboard: [caf priority: p2][CR 786373])

We tried with fix from bug 1069452 and we are still seeing 1060ms for Contact app launch latency on msm8226(4 cores and 1GB RAM) with following gaia/gecko in v2.1. 


I also saw that Mozilla is also hitting 1052ms for Contact launch latency in 

Please note that we didn't see any significant gain in launch latency when we moved from dual core(msm8610) to four core(msm8226). 

Please also look into bug 1074783 comment 19.

But Android is showing 594ms for contact app launch latency on same platform.

We need to improve Contact app launch latency to match with Android on same platform
blocking-b2g: --- → 2.2?
Blocks: 1079506
triage: this is actually a new feature. 
removing the nom and nom to feature-b2g instead.
blocking-b2g: 2.2? → ---
feature-b2g: --- → 2.2?
2.2 feature tracking.
feature-b2g: 2.2? → 2.2+
No longer blocks: B2G-Multicore
Depends on: 1103446
Depends on: 1107259
No longer blocks: AppStartup
Depends on: AppStartup
Blocks: AppStartup
No longer depends on: AppStartup
Depends on: 835679
Summary: Contact app launch latency is worse compared to Android on quad core 1 GB device → [meta] Contact app launch latency is worse compared to Android on quad core 1 GB device
Please remove 2.2+ since this bug is not in the scope.
Flags: needinfo?(bchien)
As discussion with Kevin and Ken, this is in v2.2 feature scope. Marked this for scope tracking.
Flags: needinfo?(bchien)
Flags: in-moztrap?(edchen)
QA Contact: edchen
QA Whiteboard: [COM=Gaia::Contacts][2.2-feature-qa+]
Assignee: nobody → bchien
blocking-b2g: --- → 2.2?
feature-b2g: 2.2+ → ---
Triage: Blocking on a meta-bug is too risky: you can't know how many blockers you have left before shipping and it makes the approval process harder to follow.

We recommend to nominate all the actual performance bugs.
blocking-b2g: 2.2? → -
blocking-b2g: - → ---
tracking-b2g: --- → +
Whiteboard: [CR 786373]
Whiteboard: [CR 786373] → [caf priority: p2][CR 786373]
Flags: in-moztrap?(edchen) → in-moztrap-
No longer blocks: CAF-v3.0-FL-metabug
CAF (Inder) expressed a preference to track performance meta bugs like these instead of their more granular blockers since, in their opinion, the individual blockers tend to change and don't always reflect a direct connection to the primary performance issue. CAF will track and update (close) these bugs when the reported performance issue is resolved.
Cold launch time (Visually Loaded) on Flame:
Datazilla    Master    v2.2    v2.1
Camera       1375      1383    1634
Clock        1266      1164    1041
Contacts      860       806     883
FM Radio      627       554     542
Gallery      1000       940     969
Messages     1392      1255    1262
Music        1312      1164     929 
Phone         615       554     567
Settings     2537      2573    2586
Video        1054      1022     964
[Tracking Requested - why for this release]:
No longer blocks: CAF-v2.2-metabug
No longer blocks: 1079506
Last update as followings, and Raptor dashboard [1]. Mark worksforme per no longer 2.2 blocker. Please follow bug 1194694 in v2.5.

appName   master  v2.2
--------  ------  ----
Messages  1700    986
Video     1127    1020
Settings  2682    2437
FM Radio  707     496
Gallery   1076    1046
Music     1085    956
E-Mail    463     1973
Contacts  1118    717
Clock     1202    1206
Calendar  1476    1342
Camera    1668    1297

[1] http://raptor.mozilla.org/#/dashboard/file/raptor.json
Closed: 4 years ago
Resolution: --- → WORKSFORME
See Also: → 1194694
You need to log in before you can comment on or make changes to this bug.