Closed Bug 738047 Opened 12 years ago Closed 12 years ago

Native Sync form history engine is slow

Categories

(Firefox for Android Graveyard :: Android Sync, defect, P1)

All
Android
defect

Tracking

(blocking-fennec1.0 -)

RESOLVED FIXED
Tracking Status
blocking-fennec1.0 --- -

People

(Reporter: nalexander, Assigned: nalexander)

References

Details

Android Sync should use the ContentProviderClient interface to speed up access times for the form history engine.
Priority: P2 → P1
One second per record is sadness.
It's actually much worse on my Transformer Prime, more like 4s per insert.  That's in a bulkInsert, so the CP should be reachable the whole time and no process switching should happen.  wesj suggests that Fennec is opening the DB on every access, so I'm going to block this ticket on a new ticket.
Depends on: 740218
adding to mobile triage radar.   bug 740218 is already marked dependent and flagged to block as well.
blocking-fennec1.0: --- → ?
blocking-fennec1.0: ? → -
Closing this unless Bug 740218 doesn't work out.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → INCOMPLETE
There will be additional code for this, so I'm going to re-open.
Status: RESOLVED → REOPENED
Resolution: INCOMPLETE → ---
Assignee: nobody → nalexander
With

https://github.com/mozilla-services/android-sync/pull/163

this is very snappy for me (on the Transformer Prime that kicked off the whole mess).  Will leave for QA to verify or rnewman to close.
Depending on that bug; can evaluate when it's landed.
Depends on: 742104
No longer depends on: 740218
Since the dependency has landed and qa'ed, let's close this.
Status: REOPENED → RESOLVED
Closed: 12 years ago12 years ago
Resolution: --- → FIXED
Product: Mozilla Services → Android Background Services
Product: Android Background Services → Firefox for Android
Product: Firefox for Android → Firefox for Android Graveyard
You need to log in before you can comment on or make changes to this bug.