Don't start gRPC default egress reactor until it is needed

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
    • None

      When we start the gRPC transport layer for egress communication, we always start the default reactor. However, this is only needed if we are using gRPC in sync mode, as async mode will always have a reactor provided. The polling loop of this reactor takes up 2.5% of total CPU time even though it is never used, and so we should only start it when it is first needed.

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

                Created:
                Updated: