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."],[[["This page lists the available versions of `GrpcBackgroundThreadsFactoryOption`, ranging from the latest release candidate `2.37.0-rc` down to version `2.10.1`."],["The application can provide its own `BackgroundThreadsFactory` to gain more control over threads and handle background work, which is typically done by creating a background thread and a `CompletionQueue`."],["`GrpcBackgroundThreadPoolSizeOption`, `GrpcCompletionQueueOption`, and `GrpcBackgroundThreadsFactoryOption` are mutually exclusive, with the latter being ignored if `GrpcCompletionQueueOption` is set."],["The content describes the change in version 2.18.0, where the `BackgroundThreadsFactory` was introduced and explains how connections will perform background work on behalf of the application."],["`BackgroundThreadsFactory` is an alias of type on this page."]]],[]]
