Investigate changes in SPM-3716: Expose existing memory tracking metrics from query subsystem

XMLWordPrintableJSON

    • Type: Investigation
    • Resolution: Declined
    • Priority: Major - P3
    • No version
    • Affects Version/s: None
    • Component/s: None
    • None
    • Not Needed
    • Developer Tools

      Original Downstream Change Summary

      Needs fields in explain, currentOp and slow query logs.

      Description of Linked Ticket

      Epic Summary

      Summary

      The query subsystem already performs a some memory tracking in order to spill the most resource-intensive plan stages to disk. Building on the POC Charlie did in WRITING-16628, we would like to expose these metrics so that we can build well-informed workload management policies for the server. In addition to the metrics the POC explored (per-operation, slow query, global memory utilization), we should also bubble these metrics up per PlanExecutor (cursor) so that we most effectively write a policy using the mechanism developed in PM-3701.

      Motivation

      OOO Analysis

      Documentation

      Product Description
      Scope
      Technical Design
      Docs Update

            Assignee:
            Unassigned
            Reporter:
            Backlog - Core Eng Program Management Team
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: