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

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

    • Type: Icon: Improvement Improvement
    • Resolution: Unresolved
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Networking & Observability
    • N&O Prioritized List
    • 2

      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 Unassigned
            Reporter:
            erin.mcnulty@mongodb.com Erin McNulty
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: