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 page documents the `GrpcBackgroundThreadsFactoryOption` across multiple versions, ranging from the latest release candidate 2.37.0-rc down to version 2.10.1."],["Version 2.13.0 introduced the ability for applications to provide a custom `BackgroundThreadsFactory` to gain finer control over background threads, which are normally used for performing work on behalf of the application."],["When using a custom `BackgroundThreadsFactory`, the application is responsible for creating threads blocked on its `CompletionQueue::Run()`."],["`GrpcBackgroundThreadPoolSizeOption`, `GrpcCompletionQueueOption`, and `GrpcBackgroundThreadsFactoryOption` are mutually exclusive, and `GrpcBackgroundThreadsFactoryOption` is ignored if `GrpcCompletionQueueOption` is used."],["The `BackgroundThreadsFactory` is a type alias."]]],[]]
