Going through the query planner is significantly slower than hand crafting a distinct plan

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Fixed
    • Priority: Major - P3
    • 8.1.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Query Optimization
    • Fully Compatible
    • QO 2024-09-30, QO 2024-10-14
    • 0
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      BF-35092 shows that going through the query planner (getExecutorFind) instead of the traditional distinct code path can add significant overhead to a simple single solution query (distinct() on a single field with one index, no filter or sort).

              Assignee:
              Henri Nikku
              Reporter:
              Henri Nikku
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: