Connections need to perform background work on behalf of the application. Normally they just create a background thread and a CompletionQueue for this work, but the application may need more fine-grained control of their threads.
In this case the application can provide its own BackgroundThreadsFactory and it assumes responsibility for creating one or more threads blocked on its CompletionQueue::Run().
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-03-05 UTC."],[[["The latest version available is 2.37.0-rc, with numerous previous versions, such as 2.36.0, 2.35.0, and so on, down to 2.10.1, also accessible."],["`BackgroundThreadsFactory` can be customized by applications to manage background work threads and `CompletionQueue` operations more granularly."],["Connections commonly create a background thread and a `CompletionQueue` for background work, but applications can take more control by supplying their own `BackgroundThreadsFactory`."],["The `GrpcBackgroundThreadsFactoryOption` is mutually exclusive with `GrpcCompletionQueueOption`, and is ignored if `GrpcCompletionQueueOption` is active, also note that it is mutually exclusive with `GrpcBackgroundThreadPoolSizeOption`."]]],[]]
