822719 - (Dialer-Startup) [meta] Dialer application startup needs improvement

Status: RESOLVED FIXED

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

Description

[Etienne Segonzac (:etienne)]

Meta bug to track the various dailer performance improvements.

Comment 1

[Dietrich Ayala (:dietrich)]

The child bugs here are closed, yet i was about to file a bug about dialer startup being too slow.

I always see the screenshot for ~2 seconds when starting the dialer cold. And after that I often see some sluggishness in the first few numbers I touch.

What else can we do?

Comment 2

[Etienne Segonzac (:etienne)]

(In reply to Dietrich Ayala (:dietrich) from comment #1)
> What else can we do?

Lazy load the facebook stuffs (IIRC we have about 200ms to gain here).

Comment 3

[Dietrich Ayala (:dietrich)]

I think we need some kind of bug to block on dialer startup perf. It has a higher bar than most any other app for instant response time.

Comment 4

[David Scravaglieri [:scravag]]

José, we still have issues about Diale performance, could you investigate on this please ?

Comment 5

[[:fabrice] Fabrice Desré]

Jim, can you take a look?

Comment 6

[Jim Porter (:squib)]

Sure, I can try. Has anyone else done research into this, aside from comment 2? I don't want to replicate others' work if they've already determined where we're spending the most time.

Comment 7

[Jim Porter (:squib)]

I'm going to need a SIM card for doing real-world performance tests. I recall people saying that T-Mobile has a decent plan that we can expense. However, I'm not sure which one is the ideal. Does anyone know?

(In the short term, I could always use my personal SIM card, but it's a little worrying to be using that on a phone I'm messing around with.)

Comment 8

[Dietrich Ayala (:dietrich)]

Is this less than 1 second now? Can it be closed?

Comment 9

[[e-mail]]

It is fine if the launch time is 1 sec. However, the Dialer app can get killed during memory pressure. We strongly prefer to keep this app persistent and not killed by the LMK.
We have observed that, incoming call is taking more time (~4sec) when the User is actively interacting with device (scrolling actively on Browser web page). So, keeping dialer app in background will definitely help in such scenarios.

Comment 10

[[e-mail]]

*Correction: If the launch time is below 1 sec.

Comment 11

[Dietrich Ayala (:dietrich)]

Thanks. Is there a bug for making Dialer persistent?

Comment 12

[Dietrich Ayala (:dietrich)]

(In reply to [e-mail] from comment #9)
> We have observed that, incoming call is taking more time (~4sec) when the
> User is actively interacting with device (scrolling actively on Browser web
> page).

Actually, please file a bug to find and fix the reason *why* it takes ~4s to load up dialer in that circumstance, while only ~1s otherwise.

Persistence of Dialer is a proscriptive solution. We should identify the source of the delayed load.

Comment 13

[Dietrich Ayala (:dietrich)]

godavari, where is dialer app relative to target performance? did you file a bug for dialer taking 4s for incoming call? please inform whether this bug can be closed or not.

Comment 14

[Dietrich Ayala (:dietrich)]

Confirmed that we can close this bug for dialer cold start.

Bug 812059 is where we're dealing with the incoming call scenario.