ExportXMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Query Execution
    • QE 2026-11-23
    • 200
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Each accumulator embeds its own SimpleMemoryUsageTracker, which adds roughly 100 bytes of overhead per accumulator instance. That overhead adds up in a $group with many keys, because every group key holds one instance per accumulator.  The same base class is used by accumulators that back window functions. Accumulators don't need most of what the tracker provides. They only compare their own usage against a local limit. They have no parent tracker, so they never sync with the operation-level tracker or report to CurOp. They also never report a peak, because nothing reads an accumulator's peak. GroupProcessorBase only reads the current in-use figure through getMemUsage() and charges the difference to its own stage tracker. A plain byte counter and a MemoryUsageLimit give the same observable behaviour, and the stage-level tracker still reports memory use, peak and the operation limit as before.

            Assignee:
            Foteini Alvanaki
            Reporter:
            Foteini Alvanaki
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: