Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-94960

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

    • Type: Icon: Task Task
    • Resolution: Unresolved
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Query Optimization
    • QO 2024-09-30
    • 0

      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@mongodb.com Henri Nikku
            Reporter:
            henri.nikku@mongodb.com Henri Nikku
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated: