Uploaded image for project: 'WiredTiger'
  1. WiredTiger
  2. WT-4307

Mitigate overhead from copying keys when creating transaction op structure

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major - P3
    • Resolution: Done
    • None
    • None
    • None
    • 1
    • Storage Engines 2018-09-24, Storage Engines 2018-10-08

    Description

      In order to support long running prepared transactions, we allow pages with prepared updates to be evicted. To support that, we need to know the key when resolving a prepared transaction to find the update in the lookaside file again.

      We recently introduced code to always copy the key when populating a WT_TXN_OP structure - that adds a performance penalty for transactions that never prepare, since their updates can't be evicted.

      We should investigate paths to avoid the copy in the common case.

      Attachments

        Issue Links

          Activity

            People

              sulabh.mahajan@mongodb.com Sulabh Mahajan
              alexander.gorrod@mongodb.com Alexander Gorrod
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: