Time that clients should wait before adjusting the target rate again. If clients adjust rate too frequently, the impact of the previous adjustment may not have been taken into account and may over-throttle or under-throttle. If clients adjust rate too slowly, they will not be responsive to load changes on server side, and may over-throttle or under-throttle.
↳ factor
float
If it has been at least one period since the last load adjustment, the client should multiply the current load by this value to get the new target load. For example, if the current load is 100 and factor is 0.8, the new target load should be 80. After adjusting, the client should ignore factor until another period has passed. The client can measure its load using any unit that's comparable over time. For example, QPS can be used as long as each request involves a similar amount of work.
getPeriod
Time that clients should wait before adjusting the target rate again.
If clients adjust rate too frequently, the impact of the previous
adjustment may not have been taken into account and may
over-throttle or under-throttle. If clients adjust rate too slowly, they
will not be responsive to load changes on server side, and may
over-throttle or under-throttle.
Time that clients should wait before adjusting the target rate again.
If clients adjust rate too frequently, the impact of the previous
adjustment may not have been taken into account and may
over-throttle or under-throttle. If clients adjust rate too slowly, they
will not be responsive to load changes on server side, and may
over-throttle or under-throttle.
If it has been at least one period since the last load adjustment, the
client should multiply the current load by this value to get the new target
load. For example, if the current load is 100 and factor is 0.8, the new
target load should be 80. After adjusting, the client should ignore
factor until another period has passed.
The client can measure its load using any unit that's comparable over time.
For example, QPS can be used as long as each request involves a similar
amount of work.
Returns
Type
Description
float
setFactor
If it has been at least one period since the last load adjustment, the
client should multiply the current load by this value to get the new target
load. For example, if the current load is 100 and factor is 0.8, the new
target load should be 80. After adjusting, the client should ignore
factor until another period has passed.
The client can measure its load using any unit that's comparable over time.
For example, QPS can be used as long as each request involves a similar
amount of work.
[[["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-08-28 UTC."],[],[],null,["# Cloud Bigtable V2 Client - Class RateLimitInfo (2.17.1)\n\nVersion latestkeyboard_arrow_down\n\n- [2.17.1 (latest)](/php/docs/reference/cloud-bigtable/latest/V2.RateLimitInfo)\n- [2.17.0](/php/docs/reference/cloud-bigtable/2.17.0/V2.RateLimitInfo)\n- [2.16.0](/php/docs/reference/cloud-bigtable/2.16.0/V2.RateLimitInfo)\n- [2.15.0](/php/docs/reference/cloud-bigtable/2.15.0/V2.RateLimitInfo)\n- [2.14.0](/php/docs/reference/cloud-bigtable/2.14.0/V2.RateLimitInfo)\n- [2.13.0](/php/docs/reference/cloud-bigtable/2.13.0/V2.RateLimitInfo)\n- [2.12.0](/php/docs/reference/cloud-bigtable/2.12.0/V2.RateLimitInfo)\n- [2.11.1](/php/docs/reference/cloud-bigtable/2.11.1/V2.RateLimitInfo)\n- [2.9.1](/php/docs/reference/cloud-bigtable/2.9.1/V2.RateLimitInfo)\n- [2.8.0](/php/docs/reference/cloud-bigtable/2.8.0/V2.RateLimitInfo)\n- [2.7.0](/php/docs/reference/cloud-bigtable/2.7.0/V2.RateLimitInfo)\n- [2.6.3](/php/docs/reference/cloud-bigtable/2.6.3/V2.RateLimitInfo)\n- [2.5.0](/php/docs/reference/cloud-bigtable/2.5.0/V2.RateLimitInfo)\n- [2.4.0](/php/docs/reference/cloud-bigtable/2.4.0/V2.RateLimitInfo)\n- [2.3.0](/php/docs/reference/cloud-bigtable/2.3.0/V2.RateLimitInfo)\n- [2.2.1](/php/docs/reference/cloud-bigtable/2.2.1/V2.RateLimitInfo)\n- [2.1.0](/php/docs/reference/cloud-bigtable/2.1.0/V2.RateLimitInfo)\n- [2.0.1](/php/docs/reference/cloud-bigtable/2.0.1/V2.RateLimitInfo)\n- [1.32.1](/php/docs/reference/cloud-bigtable/1.32.1/V2.RateLimitInfo)\n- [1.31.1](/php/docs/reference/cloud-bigtable/1.31.1/V2.RateLimitInfo)\n- [1.30.0](/php/docs/reference/cloud-bigtable/1.30.0/V2.RateLimitInfo)\n- [1.29.2](/php/docs/reference/cloud-bigtable/1.29.2/V2.RateLimitInfo)\n- [1.28.3](/php/docs/reference/cloud-bigtable/1.28.3/V2.RateLimitInfo)\n- [1.27.0](/php/docs/reference/cloud-bigtable/1.27.0/V2.RateLimitInfo)\n- [1.26.2](/php/docs/reference/cloud-bigtable/1.26.2/V2.RateLimitInfo)\n- [1.25.0](/php/docs/reference/cloud-bigtable/1.25.0/V2.RateLimitInfo)\n- [1.24.1](/php/docs/reference/cloud-bigtable/1.24.1/V2.RateLimitInfo)\n- [1.23.0](/php/docs/reference/cloud-bigtable/1.23.0/V2.RateLimitInfo)\n- [1.22.2](/php/docs/reference/cloud-bigtable/1.22.2/V2.RateLimitInfo)\n- [1.21.1](/php/docs/reference/cloud-bigtable/1.21.1/V2.RateLimitInfo)\n- [1.20.3](/php/docs/reference/cloud-bigtable/1.20.3/V2.RateLimitInfo) \nReference documentation and code samples for the Cloud Bigtable V2 Client class RateLimitInfo.\n\nInformation about how client should adjust the load to Bigtable.\n\nGenerated from protobuf message `google.bigtable.v2.RateLimitInfo`\n\nNamespace\n---------\n\nGoogle \\\\ Cloud \\\\ Bigtable \\\\ V2\n\nMethods\n-------\n\n### __construct\n\nConstructor.\n\n### getPeriod\n\nTime that clients should wait before adjusting the target rate again.\n\nIf clients adjust rate too frequently, the impact of the previous\nadjustment may not have been taken into account and may\nover-throttle or under-throttle. If clients adjust rate too slowly, they\nwill not be responsive to load changes on server side, and may\nover-throttle or under-throttle.\n\n### hasPeriod\n\n### clearPeriod\n\n### setPeriod\n\nTime that clients should wait before adjusting the target rate again.\n\nIf clients adjust rate too frequently, the impact of the previous\nadjustment may not have been taken into account and may\nover-throttle or under-throttle. If clients adjust rate too slowly, they\nwill not be responsive to load changes on server side, and may\nover-throttle or under-throttle.\n\n### getFactor\n\nIf it has been at least one `period` since the last load adjustment, the\nclient should multiply the current load by this value to get the new target\nload. For example, if the current load is 100 and `factor` is 0.8, the new\ntarget load should be 80. After adjusting, the client should ignore\n`factor` until another `period` has passed.\n\nThe client can measure its load using any unit that's comparable over time.\nFor example, QPS can be used as long as each request involves a similar\namount of work.\n\n### setFactor\n\nIf it has been at least one `period` since the last load adjustment, the\nclient should multiply the current load by this value to get the new target\nload. For example, if the current load is 100 and `factor` is 0.8, the new\ntarget load should be 80. After adjusting, the client should ignore\n`factor` until another `period` has passed.\n\nThe client can measure its load using any unit that's comparable over time.\nFor example, QPS can be used as long as each request involves a similar\namount of work."]]