Investigate allocation patterns for oplog visibility data structure

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Replication
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      As noted in the merge-to-master PR here,

      a future effort should investigate std::list vs. boost::intrusive (though std::list is also intrusive, typically) and their allocation patterns - and should probably include a slab allocation strategy so we don't scatter these list elements all over memory. (better locality can hugely improve performance)

            Assignee:
            Unassigned
            Reporter:
            Kyra Ramesh Krishna
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated: