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

Optimize OpDebug in CurOp to remove any unneeded metrics in reporting

    • Type: Icon: Task Task
    • Resolution: Unresolved
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Server Programmability

      Currently CurOp is a very large object being initialized and destructed every operation. In CurOp there are quite a few objects, However 85% of the object is taken up by two objects inside.

      OpDebug_debug and boost::optional<SingleThreadedLockStats> _lockStatsBase

      OpDebug contains a multitude of metrics stored throughout an operations life cycle, and is used for reporting and logging. We need to look over all metrics and see which ones are needed, and which ones can be removed  to reduce the bloat of CurOp

            Assignee:
            Unassigned Unassigned
            Reporter:
            dominic.hernandez@mongodb.com Dominic Hernandez
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated: