929996 - [e.me] Loading first E.me file takes too long

Status: RESOLVED FIXED

(Firefox OS Graveyard :: Gaia::Everything.me, defect, P2)

Description

[Amir Nissim (:amirn)]

setup:
connect a FXOS device to computer and run 'adb logcat | grep EVME'

STR:
1. restart 'homescreen' so E.me files are not loaded
2. click a collection
3. observe that several seconds pass until the first E.me file is loaded (first log message by E.me)
4. after the first file loads, the rest of the files load faster

Expected:
The first file is loaded immediately after the click event

Comment 1

[Amir Nissim (:amirn)]

Evyatar, can you please provide more information?

Comment 2

[Evyatar 'Tron' Amitay (everything.me)]

No more info about this. it's something we witnessed while working on 1.2 - the first files being loaded take up to a few hundred ms, and then the following files are almost instant (usually an avg of 20ms).

I did some debugging on this, and it's really just the loading of the file that takes long. even if you load empty JS files - the first ones will take a lot of time.

Comment 3

[Amir Nissim (:amirn)]

Who is the right person to assign this?

Comment 4

[Mike Lee [:mlee]]

Amir,
We're tracking this issue in our backlog but are currently focused on 1.2 blockers this sprint (11.08). I'm noming this for 1.3 so we can triage and find an assignee after 11.08.

Comment 6

[Dave Huseby [:huseby]]

We minus for v1.3 because the scope of the problem is limited to the first load and the impact is just a few hundred milliseconds.  We should fix it, but it's not of a magnitude that justifies blocking v1.3.

Comment 7

[Ran Ben Aharon [:ranbena] EverythingMe]

Dave, I'd like you to reconsider as I believe fixing this issue would gain seconds (not mili) of loading time.

Notice that it's quite ok when clicking on the search bar for the first time (on every boot) but it's much more apparent when opening a Collection or adding a new one. It can lead up to accumulated 7+ seconds of progress indicator as the e.me server requires init and communication.

Comment 8

[Dave Huseby [:huseby]]

Yes you are right there is a problem.  The 1.3 minus just means we won't hold up the 1.3 release.  This bug should get fixed but before we do that, can you profile it and get some solid data.  Here's the documentation for the profiler we use: https://developer.mozilla.org/en-US/docs/Performance/Profiling_with_the_Built-in_Profiler

If you need help interpreting the results, attach them here and needinfo me again and I'll see what I can do to help you.

Comment 9

[Ran Ben Aharon [:ranbena] EverythingMe]

Hey Dave, I can't user profiler.sh as we don't build our own b2g and using the Nightly profiler doesn't seem to yield any informative results.

I think it's better I let the perf pros handle this.

Comment 10

[Dave Huseby [:huseby]]

I won't be able to get to this until February.  Is there are reason you are not building your own b2g?

Comment 11

[Ran Ben Aharon [:ranbena] EverythingMe]

We've never needed to and the times we tried installing it and all it's dependencies were very difficult and time consuming.

Comment 12

[Amir Nissim (:amirn)]

No longer relevant in Vertical homescreen.