[
https://issues.apache.org/jira/browse/CB-2637?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bas Bosman updated CB-2637:
---------------------------
Component/s: Plugin Contacts
> Speed up contacts find by ignoring entries with specified null fields
> ---------------------------------------------------------------------
>
> Key: CB-2637
> URL: https://issues.apache.org/jira/browse/CB-2637
> Project: Apache Cordova
> Issue Type: Improvement
> Components: Android, Plugin Contacts
> Reporter: Nestor Soign
> Labels: contacts
>
> Finding contacts is very slow: roughly 1 second per 100 contacts on recent
> hardware. According to https://issues.apache.org/jira/browse/CB-1250 the
> current major speed limitation is the number of contacts returned by find.
> I have noticed that a large percentage of contacts appear to be either
> incomplete or lack email addresses or phone numbers, since Google combines
> phone and email contacts into a single list.
> Many applications may be interested only in contacts which have phone numbers
> or which have email, or which have either. By allowing specification of
> fields which are required to be non-null, contacts.find calls could be sped
> up significantly for those cases.
> For example, I have a contacts list with 2641 contacts in it. Of those, 614
> have telephone numbers but no emails. 1134 have emails but no telephone
> numbers. 203 have both emails and telephone numbers, and the remainder appear
> to be malformed and useless.
> A contacts.find call on my phone (HTC EVO 4G LTE running Android 4.1.1) takes
> about 13 seconds to complete, but if it could be limited to only contacts
> with telephone numbers, it would probably take about 3-4 seconds. Even if it
> were limited to contacts with either a telephone number or an email, it would
> probably take about 9-10 seconds, still a substantial improvement.
> If this is easy to implement it would be very helpful in many applications.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
