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

Cache btree's ckptlist between checkpoints

    • Type: Icon: Improvement Improvement
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • WT10.0.1, 4.4.7, 5.0.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • Labels:
    • 8
    • Storage - Ra 2021-04-19, Storage - Ra 2021-05-03, Storage - Ra 2021-05-17, Storage - Ra 2021-05-31
    • v4.2

      First part of work tracked from WT-7285:

      Investigate how we are going to store the checkpoint information, I like the idea proposed by Susan LoVerso, so would start with keeping 1 (or 2) ckpt structures around attached to the dhandle. The cached ckpt structures will be used instead of reparsing the strings, and then updated as new checkpoints get created. Let's start with the common (non-backup) path. In the debug build, we will still parse and create ckpt structures and assert if the structures created from metadata do not match the one we hold in the cache. We will need to figure exactly how many ckpt structures to keep around, including handling checkpoint deletion.

            sulabh.mahajan@mongodb.com Sulabh Mahajan
            sulabh.mahajan@mongodb.com Sulabh Mahajan
            0 Vote for this issue
            7 Start watching this issue