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

Change opCtx waits to always use the fastclock

    • Service Arch
    • Fully Compatible

      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.

            Assignee:
            backlog-server-servicearch [DO NOT USE] Backlog - Service Architecture
            Reporter:
            mira.carey@mongodb.com Mira Carey
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: