1031315 - [Contacts][Data Refactor]Check performance of building contact details from different DS

Status: RESOLVED FIXED

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

Description

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

We need to know what's the performance of building a contact details view from a MultiContact (pointer to different DataStores) and merge in a single view.

This will help us to decide if we need local information for the contacts app or we can affort to go for each source in real time and compose the contact each time the user wants to look at it.

Comment 1

[Jose Manuel Cantera]

In the branch below, there is an app named 'contactsidb' that can be used to compare the performance of getting an already cooked contact from indexedDB against building the contact on the fly getting the data from the GCDS and two slave datastores: 

https://github.com/jmcanterafonseca/gaia/tree/contacts_perf_idb

The conclusions are that cooking a contact (that comes from 2 different datastores) can be 4 or 5 times slower, than getting the same contact data from an indexedDB that has all the data already cooked.

Comment 2

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

(In reply to Jose Manuel Cantera from comment #1)
> In the branch below, there is an app named 'contactsidb' that can be used to
> compare the performance of getting an already cooked contact from indexedDB
> against building the contact on the fly getting the data from the GCDS and
> two slave datastores: 
> 
> https://github.com/jmcanterafonseca/gaia/tree/contacts_perf_idb
> 
> The conclusions are that cooking a contact (that comes from 2 different
> datastores) can be 4 or 5 times slower, than getting the same contact data
> from an indexedDB that has all the data already cooked.

Great!

Thanks for sharing the results!