Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-38211

Optimise duplicate check algorithm for timestamp safe unique index

    XMLWordPrintableJSON

Details

    • Icon: Improvement Improvement
    • Resolution: Won't Fix
    • Icon: Major - P3 Major - P3
    • None
    • None
    • Storage
    • Storage Engines 2019-05-20, Storage Engines 2019-06-03
    • 0
    • 8

    Description

      Timestamp safe unique index for 4.2 incorporates a duplicate key check/prevention algorithm. Older Unique index used to prevent duplicate keys in a different way. We put this algorithm to be timestamp safe.

      Linkbench (LOAD_NODE_BULK) shows a performance penalty due to this check. This ticket tracks the effort in optimising the algorithm and get the performance back.

      Attachments

        1. batch_ins.py
          1 kB
        2. linkbench_simu.py
          4 kB
        3. uniq_idx.py
          4 kB
        4. uniq_idx.sh
          2 kB

        Activity

          People

            sulabh.mahajan@mongodb.com Sulabh Mahajan
            sulabh.mahajan@mongodb.com Sulabh Mahajan
            Votes:
            0 Vote for this issue
            Watchers:
            10 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: