Details
-
Improvement
-
Status: Open
-
Major
-
Resolution: Unresolved
-
None
-
None
-
None
Description
Right now, we collect the update operations in batches, but then issue individual update operations.
A special-case API that takes a set of updates and applies them in a single DB operation might speed up things, in particular when there's a network hop.
Related to this, we may want to think about whether we need to attach a modified check to each single operation (by keeping the _modified value for each _id). Wouldn't it be sufficient to just check that the _modified value is not newer than the end of the time window for the VGC run?
Attachments
Attachments
Issue Links
- relates to
-
OAK-5704 VersionGC: reset _deletedOnce for documents that have been resurrected
- Closed