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

Consider removing _isCancelled calls in read/write for gRPC sessions

XMLWordPrintableJSON

    • Type: Icon: Task Task
    • Resolution: Unresolved
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Labels:
      None
    • Service Arch

      Calling _isCancelled in gRPC actually requires a pop off of the gRPC completion queue (aka a synchronization). When I removed it from calls to source and sink Message in grpcSession, I saw improvements of about ~70ms in local benchrun testing for a findOne.

      Consider removing this call/reconsidering this implementation.

            Assignee:
            backlog-server-servicearch [DO NOT USE] Backlog - Service Architecture
            Reporter:
            erin.mcnulty@mongodb.com Erin McNulty
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: