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

Measure opLatencies with workingMillis

XMLWordPrintableJSON

    • Type: Icon: Task Task
    • Resolution: Duplicate
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Storage Execution

      opLatencies are currently set with durationMillis here and here. It might make sense to exclude lock and ticket wait times from opLatencies similar to workingMillis. We may consider adding another metric like opDuration that continues reporting based on durationMillis.

            Assignee:
            shinyee.tan@mongodb.com Shin Yee Tan
            Reporter:
            shinyee.tan@mongodb.com Shin Yee Tan
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: