Closed Bug 817116 Opened 12 years ago Closed 11 years ago

[meta][Gaia::Video] Long initial startup time for Video app

Categories

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

All
Gonk (Firefox OS)
defect

Tracking

(Not tracked)

RESOLVED FIXED
B2G C3 (12dec-1jan)

People

(Reporter: pla, Unassigned)

References

Details

(Keywords: meta, perf, Whiteboard: interaction [target:12/21], [FFOS_perf])

What makes it feel slow/broken?
It takes too long to startup the Video app after a reset.  Timed at 5 seconds on Unagi running Nov. 22 nightly.  David Clarke to provide more accurate, recent numbers.

Did it prevent you from doing what you wanted? Why?

How does this make you feel?

[ ]  :)  I feel happy about it
[ ]  :|  Meh
[X]  :(  I'm upset
[ ] >:O  I'm angry

Device: Original numbers from Unagi, Nov. 22 nightly.  David Clarke to get Otoro numbers.

Details:

B2G on Unagi:               5 seconds
Android ICS 4.0.4 on Otoro: 1 second

David Clarke to provide updated B2G on Otoro numbers.

Bonus: can you attach a video of the problem?
See metabug 814981
blocking-basecamp: --- → ?
BB+, P3 - performance. 5 seconds is quite long to launch an app
blocking-basecamp: ? → +
Priority: -- → P3
This bug seems like a meta bug and we don't block on meta bug. Someone need to investigate the reasons why it is slow and open blocking bugs that blocks this one.

Also the exact timing method should be described so the people that are going to work on it will be able to compare.

Renominating and triagers please explain why we block on a meta bug.
blocking-basecamp: + → ?
Hey Gabriele, could you investigate to see what is slow please ?
Flags: needinfo?(gsvelto)
(In reply to dscravaglieri from comment #3)
> Hey Gabriele, could you investigate to see what is slow please ?

Sure, I've run a full profile of the app while starting up, I've done it on my Otoro using this morning's code for building both Gaia and Gecko. Unfortunately I don't have an Unagi yet so I can't test on that device. The first thing I noticed is that when launching the video app it starts from scratch, it does not re-use the pre-launched process that we normally use to speedup starting applications. I'm not sure why this is happening as all applications should be launched through it, but it's adding ~600ms to the startup time. Fixing it should bring a nice improvement.


The full profile trace can be found here:

http://people.mozilla.com/~bgirard/cleopatra/#report=2875c75031045a3affd0ca089e63f6f7857673e8

The entire application startup takes 2 seconds which is pretty good but could be better if pre-launched. The various phases are not taking much time:

- Page layout (including CSS processing) is taking only 80ms

- Screen painting is taking a very small amount of time, the samples are 10ms which means it could be even less

- Scanning for videos and generating the thumbnails seems to be taking ~500ms in total and some of that time is waiting for I/O (~80ms). My phone has only the two default videos so this might take longer on another device. I can try if there's interest.

- The rest is scattered among many small bits, the various parts of l10n seem to be taking ~100ms which is much better than a month ago
Flags: needinfo?(gsvelto)
Assignee: nobody → dale
blocking-basecamp: ? → +
Mass Modify: All un-milestoned, unresolved blocking-basecamp+ bugs are being moved into the C3 milestone. Note that the target milestone does not mean that these bugs can't be resolved prior to 12/10, rather C2 bugs should be prioritized ahead of C3 bugs.
Target Milestone: --- → B2G C3 (12dec-1jan)
This application cannot use the prelaunched process like most of the others because it needs special permissions to run, see bug 786631. I'm not putting it as a dependency because this bug is a blocker and 786631 is not.
This performance bug represents a non-trivial amount of work. Marking as a P1 issue to frontload risk.
Priority: P3 → P1
Whiteboard: interaction → interaction [target:12/21]
Can we block on specific bugs and not on [This APP is slow] fuzzy bug? This make it hard to really understand what work is ungoing and to split the work between people and between teams when it comes to front-end versus backend.

blocking-basecamp? but I belive this is a meta bug and should be bb-.
blocking-basecamp: + → ?
For the l10n part:
Blocked by bug 793034 which is minused.

Blocked by bug 814178 for media access.
blocking-basecamp: ? → ---
Depends on: 793034, 814178
Keywords: meta
Summary: [Gaia::Video] Long initial startup time for Video app → [meta][Gaia::Video] Long initial startup time for Video app
Depends on: 821691
Depends on: 780692, 820196
Whiteboard: interaction [target:12/21] → interaction [target:12/21], [FFOS_perf]
As a side-effect of bug 856542 there have been significant improvements to the time it takes to enumerate and display thumbnails for the videos.
Assignee: dale → nobody
Closing as these are below required startup time (from previous target)
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.