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

Add insight into backup size savings

    • Type: Icon: Improvement Improvement
    • Resolution: Unresolved
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Storage Engines

      In WT-12791 we now can clear incremental backup bits based on checkpoints and the extent lists. That improvement is very dependent on backup granularity size and it is hard to measure savings across runs. With that change, the blocks necessary for the existing checkpoints are the ones considered.

      This ticket should investigate keeping information about the "old" way in memory at least and providing statistics to be able to compare how much data we are now copying versus "if we didn't clear any bits".

      This new statistic could allow for experimentation with different granularity sizes.

            Assignee:
            sue.loverso@mongodb.com Susan LoVerso
            Reporter:
            sue.loverso@mongodb.com Susan LoVerso
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated: