Revisit lock contention in GRPCClient

XMLWordPrintableJSON

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

      The implementation of GRPCClient::connect currently acquires a mutex twice in the function, which has negative performance implications. We can revisit this as a performance improvement for the egress gRPC implementation if needed.

            Assignee:
            Unassigned
            Reporter:
            Erin McNulty
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: