Investigate more efficient update+replacement algorithms

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Duplicate
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Write Ops
    • None
    • Storage Execution
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Currently during an update in replacement mode (replace the whole doc) we make many copies of the data, between BSONObj mutablebson::document/elements and during oplog creation as well. We should investigate if there is a better way across the boards.

              Assignee:
              [DO NOT USE] Backlog - Storage Execution Team
              Reporter:
              Scott Hernandez (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: