Calibrate PROJECTION nodes

XMLWordPrintableJSON

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

      Currently:

      • all the PROJECTION nodes have the same cost, which I believe is incorrect. PROJECTION_COVERED should not be doing any extensive computations, it just converts the index entries into documents
      • the cost of the projection nodes does not depend on the number of columns projected.
      • the cost of PROJECTION is about the same as the cost of the COLLSCAN, which seems incorrect.

      Generally, the costs should be such that an IXSCAN + PROJECTION_COVERED should always win on the basis of cost.

            Assignee:
            Unassigned
            Reporter:
            Philip Stoev
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: