MMAPv1 should have a singleton RecordAccessTracker, rather than creating one per database

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Done
    • Priority: Major - P3
    • 2.8.0-rc3
    • Affects Version/s: 2.8.0-rc2
    • Component/s: Storage
    • None
    • Fully Compatible
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      The RecordAccessTracker allocates a large table in which it stores accessed addresses, in order to keep track of what data is likely in physical memory. In 2.6 versions, this table was global to the process. 2.8.0-rc2 creates a table per database, which can have a large memory footprint in the case that many databases are open on the server. Instead, MMAPv1 should keep a singleton RecordAccessTracker.

            Assignee:
            David Storch
            Reporter:
            David Storch
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: