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

change timing for 'dur' so it doesn't include timing for recordStats; potentially slowing down serverStatus

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major - P3 Major - P3
    • None
    • 2.2.0
    • Admin
    • ALL

    Description

      It seems that the code to generate "dur" is unchanged for 2.2.0, but the timing for "dur" includes the timing for recordStats, which is new. See dbcommands.cpp around line 651.

      suggestion: the timeBuilder for "after dur" should be done right after the "dur" section, and a separate timeBuilder should be done after recordStats. Since it is currently lumping both times together but calling it "dur"

      Attachments

        Activity

          People

            Unassigned Unassigned
            barrie Barrie Segal
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: