866676 - [Buri][Shira-48780] Contact very easy to be killed, performance low

Status: RESOLVED WONTFIX

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

Description

[sync-1]

AU_LINUX_GECKO_ICS_STRAWBERRY_V1.01.00.01.019.085
  Firefox os  v1.0.1
  Mozilla build ID:20130422230201
 
 
 +++ This bug was initially created as a clone of Bug #447428 +++
 
 Description: 
 
 Contact very easy to be killed, performance low
 
 
  DEFECT DESCRIPTION:
 
  REPRODUCING PROCEDURES:
 
  EXPECTED BEHAVIOUR:
 
  ASSOCIATE SPECIFICATION:
 
  TEST PLAN REFERENCE:
 
  TOOLS AND PLATFORMS USED:
 
  USER IMPACT:
 
  REPRODUCING RATE:
 
  For FT PR, Please list reference mobile's behavior:
 
 ++++++++++ end of initial bug #447428 description ++++++++++

Comment 1

[Francisco Jordano [:arcturus] [:francisco]]

Hi,

During past work week, we went through a heavy refactoring to improve the performance for both frontend and backend, so it need to be tested with latest versions of both parts.

As well the bug description is a bit confusing, low performance and easy to be killed are two different issues.

Could you provide us how old is the build for gecko and gaia which you are using for the tests?

Kind regards,
Francisco.

Comment 2

[Daniel Coloma:dcoloma]

tef- until the following details are provided:

 - Preconditions
 - Gaia and Gecko commit numbers
 - Observed vs. Target Performance

Comment 3

[Amelie Kong]

Sorry, we can not provide the Gaia and Gecko commit number... Our latest version build ID is  Mozilla build ID:20130422230201

I think it already includes all the optimizing patches.
For performance issue, we can refer to the Bug854365 for more detail.

Here, one main question is about, 
(1)whether we can grant Contact high priority,like Music player, which will not be killed by low memory killer so easily as now?  
(2)Or whether there is any other method , can let Contact only do list initialization once after switch on? Or regenerate the list when there is any updating.Anyway, normally, the contact will not be changed frequently. We should not spend a lot of time to rebuild the list when open contact every time.

Comment 4

[Daniel Coloma:dcoloma]

Still not clear:

 - How many contacts do you have
 - How many other apps do you have
 - Which operations you do
 - When is the contacts app killed

Comment 5

[Amelie Kong]

on version:
SW12C
AU_LINUX_GECKO_ICS_STRAWBERRY_V1.01.00.01.019.111
Firefox os  v1.0.1
Mozilla build ID:20130518070208

feedback :
i have imported 91 contacts from SIM
i have *not* imported facebook yet - which means i only have 91 contacts in
addressbook.

i switch between dialer & setting, it's very very easy to observe that they are
killed all the time... this is really bad performance which can be so easily
observed, compared to last year 256MB RAM Android 2.3 - at least a 256MB
Android won't reproduce such easily...

Comment 6

[alberto.pastor]

We are planing on improve memory performance in all the lists (including contacts). As soon as Bug 865750 lands.

Comment 7

[Ben Kelly [:bkelly, not reviewing]]

Adding dependent bugs for the contacts app improvements.  I have been testing those changes with 1000 contacts.

Note, however, these changes are a fairly significant refactoring of the contacts list.  There is some risk from the large changeset and there are some additional dependent bugs that will need to be uplifted.

Comment 8

[bhavana bajaj [:bajaj]]

Not a critical regression in 1.1, bumping to koi? for backlog consideration in 1.2.

Comment 9

[Joe Cheng [:jcheng] (please needinfo)]

please raise a new bug with latest version and better STR and separate it into 2 bugs (low memory / performance) if needed

Comment 10

[Wilfred Mathanaraj [:WDM]]

can we confirm if there was an improvement after the work we did in v1.1/v1.2 and have TCL confirm if this happens still?