Enable CPU based throttling in Bigtable client #12959
Labels
api: bigtable
Issues related to the Bigtable API.
type: feature request
‘Nice-to-have’ improvement, new feature or different behavior or design.
Sometimes batch write jobs want to optimize for CPU utilization, instead of minimizing latency or maximizing throughput.
At the moment, the servers can only communicate errors to us, such as
kDeadlineExceeded
. There is a way to set some feature flags and have the server return throttling information. They essentially tell us whether we should speed up the current QPS, or whether we should slow down the current QPS.Phase 1
RateLimiter
RateLimiter
. I am calling it theMutateRowsRateLimiter
. This thing has anUpdateRate(MutateRowsResponse const& r)
.struct experimental::BulkApplyThrottlingOption { using Type = bool; };
MutateRowsRateLimiter
through the client layersPhase 2
AsyncBulkApply
supportThe text was updated successfully, but these errors were encountered: