Closed
Bug 764246
Opened 14 years ago
Closed 13 years ago
AITC: reduce database reads when saving a record
Categories
(Cloud Services Graveyard :: Server: Sync, defect)
Cloud Services Graveyard
Server: Sync
Tracking
(Not tracked)
VERIFIED
WONTFIX
People
(Reporter: rfkelly, Assigned: rfkelly)
Details
(Whiteboard: [qa?])
Per Bug 759912, saving a record into the DB involves two reads and a write: one read in AITC code to get the existing value for "installedAt", one read in SyncStorage code to check whether we should UPDATE or INSERT, then finally the write to store the new data.
We should be able to do better, but it will require some refactoring of the storage backend to allow us to elide the second read.
Updated•14 years ago
|
Whiteboard: [qa?]
| Assignee | ||
Comment 1•13 years ago
|
||
AitC is no more
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → WONTFIX
Updated•13 years ago
|
Status: RESOLVED → VERIFIED
Updated•3 years ago
|
Product: Cloud Services → Cloud Services Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•