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

Status: RESOLVED WORKSFORME

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

Description

[Tapas[:tkundu on #b2g/gaia/memshrink/gfx] (always NI me)]

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. 

https://www.codeaurora.org/cgit/quic/lf/b2g/mozilla/gaia/commit/?h=mozilla/v2.1&id=9861c61ec302fb0316c753a2e1c0f592180515fd
https://www.codeaurora.org/cgit/quic/lf/b2g/mozilla/gecko/commit/?h=mozilla/v2.1&id=81d98fe40d10d5a8a48664aa60913491db215a4f

I also saw that Mozilla is also hitting 1052ms for Contact launch latency in 
https://wiki.mozilla.org/B2G/QA/2014-10-02_Performance_Acceptance#Contacts

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

Comment 1

[Wesley Huang [:wesley_huang] (EPM) (NI me)]

triage: this is actually a new feature. 
removing the nom and nom to feature-b2g instead.

Comment 2

[Wesley Huang [:wesley_huang] (EPM) (NI me)]

2.2 feature tracking.

Comment 3

[Thinker Li [:sinker]]

Please remove 2.2+ since this bug is not in the scope.

Comment 4

[Bobby Chien]

As discussion with Kevin and Ken, this is in v2.2 feature scope. Marked this for scope tracking.

Comment 5

[Johan Lorenzo [:jlorenzo]]

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.

Comment 6

[Mike Lee [:mlee]]

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.

Comment 7

[Bobby Chien]

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

Comment 8

[Wesley Huang [:wesley_huang] (EPM) (NI me)]

[Tracking Requested - why for this release]:

Comment 10

[Bobby Chien]

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