[ServiceWorkers] Check virtual list and model caching

RESOLVED FIXED in FxOS-S1 (26Jun)

Status

Firefox OS
Gaia
RESOLVED FIXED
3 years ago
3 years ago

People

(Reporter: arcturus, Assigned: arcturus)

Tracking

unspecified
FxOS-S1 (26Jun)

Firefox Tracking Flags

(Not tracked)

Details

We need to explore how the new virtual list:

https://github.com/etiennesegonzac/dom-scheduler

Can use a pregenerated model vial cached content in the service worker (old way of using render cache)
Blocks: 1153312

Updated

3 years ago
Whiteboard: [s3]

Updated

3 years ago
Target Milestone: --- → NGA S2 (12Jun)

Updated

3 years ago
Assignee: nobody → francisco
Status: NEW → ASSIGNED
Whiteboard: [s3]
Target Milestone: NGA S2 (12Jun) → NGA S3 (26Jun)
POC with the virtual list and caching via sw:

https://github.com/arcturus/dom-scheduler/tree/contacts-sw-cache

The way we use the render cache here is that we create a /model.json file that contains the first chunk to be render and the number of contacts.
That's the information that the list needs to do a quick first paint.

Will try another approach that is to save the information in the own index.html
Interesting results ahead:

- First paint packaged ~ 960 ms
- First paint with SW ~ 1100 ms (The SW serving is increasing the time)
- First paint with SW and Cache ~ 1000 ms (We save a bit but not much)

Will need to explore if the code added to cache, or the need of an extra request is what is not making us have a huge gain in the performance.

Updated

3 years ago
Target Milestone: NGA S3 (26Jun) → FxOS-S1 (26Jun)
Closing this as fixed, since several tests have been done.

https://github.com/arcturus/dom-scheduler/tree/contacts-test
https://github.com/arcturus/dom-scheduler/tree/contacts-sw-cache

We need to check now the performance for SW and raw cache.
Status: ASSIGNED → RESOLVED
Last Resolved: 3 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.