[Classic] Optimize large group keys

XMLWordPrintableJSON

    • Fully Compatible
    • v7.1, v7.0, v6.0, v5.0
    • QE 2023-08-21, QE 2023-09-04, QE 2023-09-18, QE 2023-10-02, QE 2023-10-16, QE 2023-10-30, QE 2023-11-13
    • 159
    • None
    • 0
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      After 4.4 we switched mongo::Document to use lazy shredding instead of eager shredding. If a customer has a large group key over large documents with potentially missing fields this can result in lots of linear look ups for each field resulting in O(n^2) type behavior. where N is the number of fields in a document. The goal of this ticket is to make a temp fix this issue for 5.0 in the classic engine since SERVER-79548 should fix this for SBE. This ticket does not make any changes to the group or project stage but adds a mechanism to opt in to the old eager document shredding

              Assignee:
              Mickey Winters
              Reporter:
              Mickey Winters
              Votes:
              1 Vote for this issue
              Watchers:
              11 Start watching this issue

                Created:
                Updated:
                Resolved: