Don't copy the tree on changes if all cursors are positioned behind it in BiggieSE

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Fixed
    • Priority: Major - P3
    • 4.1.6
    • Affects Version/s: None
    • Component/s: Storage
    • None
    • Fully Compatible
    • Storage NYC 2018-12-03
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      Currently the biggie storage engine makes a copy on write of the head tree to any pending modifications even if all the cursors are behind the master copy.
      We should avoid doing this so that we don't have to keep track of a potentially large trail of history (space and time consuming) that will be unused by the cursors when they catch up to the head again.

            Assignee:
            Gregory Wlodarek
            Reporter:
            Gregory Wlodarek
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: