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

Address regressions due to PathCompare [Eq] lowering change

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

      SERVER-80235 caused some perf regressions and my comment on SERVER-80987 describes an investigation done as to why those regressions happened. There is far more detail on that ticket, but the regressions seem to be because now there are two operators instead of one (BinaryOp + cmp3w vs BinaryOp). An idea described in the comment to address this is to have specialized cmp3w functions, one for each comparison, which do the appropriate comparison to 0 with the output of cmp3w. This may be more performant given that we always know we will be comparing against a constant for comparisons.

            Assignee:
            backlog-query-optimization [DO NOT USE] Backlog - Query Optimization
            Reporter:
            militsa.sotirova@mongodb.com Militsa Sotirova
            Votes:
            0 Vote for this issue
            Watchers:
            10 Start watching this issue

              Created:
              Updated: