Investigate TPC-H plan quality when data does not fit in cache

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Query Optimization
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      For our current TPC-H Locust workloads, the cost model always assumes that all data is in cache, and we thus end up in case 1 of Mackert-Lohman to estimate the number of random IOs.

      We should see the effect of reducing the WT cache size on plan quality & stability. If this provides significantly different results, we should consider making an actual automated variant with this smaller cache size.

            Assignee:
            Max Verbinnen
            Reporter:
            Max Verbinnen
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: