Layered tables performance improvements

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Unresolved
    • Priority: Minor - P4
    • None
    • Affects Version/s: None
    • Component/s: Layered Tables
    • Storage Engines, Storage Engines - Foundations
    • SE Foundations - Q3+ Backlog
    • None

      There are a couple of known low-hanging fruit in the layered table manager. Firstly, when draining ingest tables, we don't skip empty ingest tables. Secondly, while we're updating timestamps in order to prune the ingest table, we hold the layered table lock for pretty much the entire function. It would be possible to just copy the relevant URIs locally, then release it.

              Assignee:
              [DO NOT USE] Backlog - Storage Engines Team
              Reporter:
              Will Korteland
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: