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

Change opCtx waits to always use the fastclock

    XMLWordPrintableJSON

Details

    • Service Arch
    • Fully Compatible

    Description

      Inside the opCtx code, maxtimems and runWithDeadline times are tracked with the fast clock, but opCtx waits are tracked with the precise clock.

      If it's okay to use the fast clock for hasDeadlineExpired, it's probably okay to use it for timed waits, and we could save ourselves some cycles if it is.

      Attachments

        Activity

          People

            backlog-server-servicearch Backlog - Service Architecture
            mira.carey@mongodb.com Mira Carey
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: