Eviction algorithm for bad cached plans needs to be more aggressive

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Duplicate
    • Priority: Major - P3
    • None
    • Affects Version/s: 2.6.4
    • Component/s: Querying
    • None
    • ALL
    • Query 2.7.8
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      When we cache a plan, if subsequent queries produce significantly worse performance result than expected, the cached plan should be evicted.

      It's currently evicted but the eviction strategy is too conservative so if we happen to cache a plan that works well only on a small minority of values we take too long to replace it.

            Assignee:
            David Storch
            Reporter:
            Asya Kamsky
            Votes:
            0 Vote for this issue
            Watchers:
            8 Start watching this issue

              Created:
              Updated:
              Resolved: