Consider removing _isCancelled calls in read/write for gRPC sessions

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Networking & Observability
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      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:
              Unassigned
              Reporter:
              Erin McNulty
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated: