If set, the client will throttle mutations in batch write jobs.
This option is for batch write jobs where the goal is to avoid cluster overload and prevent job failure more than it is to minimize latency or maximize throughput.
With this option set, the server rate-limits traffic to avoid overloading your Bigtable cluster, while ensuring the cluster is under enough load to trigger Bigtable [autoscaling] (if enabled).
[[["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 provides documentation for the `BulkApplyThrottlingOption` across multiple versions of the Google Cloud C++ Bigtable library, from version 2.11.0 up to the latest release candidate 2.37.0-rc."],["`BulkApplyThrottlingOption` is used to manage and throttle mutations in batch write jobs to prevent overloading the Bigtable cluster, thus reducing the likelihood of job failures."],["This feature ensures that the cluster maintains a sufficient load to trigger Bigtable autoscaling if enabled, however latency minimization or throughput maximization is not the priority."],["The app profile associated with these requests must be configured for single-cluster routing, as detailed in the `google::cloud::bigtable::AppProfileIdOption`."],["To activate this option it needs to be supplied to `MakeDataConnection()` and is more suitable for avoiding cluster overload than minimizing latency or maximizing throughput."]]],[]]
