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"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-07-02 UTC."],[[["The latest version available is 2.37.0-rc, with numerous other versions, such as 2.36.0, 2.35.0, and so on, also accessible through provided links."],["The `BackgroundThreadsFactory` has been changed, allowing applications to exert more precise management over their threads for background work."],["Applications can provide a custom `BackgroundThreadsFactory`, taking charge of making one or multiple threads blocked on its `CompletionQueue::Run()`."],["The options `GrpcBackgroundThreadPoolSizeOption`, `GrpcCompletionQueueOption`, and `GrpcBackgroundThreadsFactoryOption` are mutually exclusive, with the latter being ignored if `GrpcCompletionQueueOption` is utilized."],["The page documents the alias `BackgroundThreadsFactory`."]]],[]]
