Output either maxTotalMemoryUsage or maxUsedMemBytes in $setWindowFields explain

XMLWordPrintableJSON

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

      SPM-3716 just added maxUsedMemBytes to the $setWindowFields explain output if the query memory tracking feature flag is on, but there is already a field in the $setWindowFields explain that represents the same value ("maxTotalMemoryUsage"). It doesn't make sense to output both so we should choose one or the other.

      We should also audit the other memory-tracked stages to see if this is a problem for other stages.

            Assignee:
            Unassigned
            Reporter:
            Erin Liang
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: