|
Rate counters are not intended to compute rates with high precision. The accuracy you can expect depends on the selected time window over which rates are calculated. As per the documentation, the estimated percentage error boundaries under nominal conditions are as follows:
|
||
| This is the RPS limit. The value must be between 10 and 10000. The lowest rate limit that can be effectively detected is 100 RPS. Using a limit below this level may result in unpredictable accuracy and detection time. If a rate limit below 100 RPS is desired, a higher Delta value can be used to achieve a lower EffectiveRate Limit. | ||
| This is the integer value to increment the entry in the rate counter by. The value must be between 0 and 1000. Typically, a value of 1 is used. If a value of 0 is used, the rate counter can be checked without incrementing it. | ||
| This is the Rate Limit divided by the Delta. Using a Delta greater than 1 effectively lowers the EffectiveRate Limit, which means less requests are needed to trigger rate limiting. | ||
| This is the Time Window Size multiplied by the Effective Rate Limit. Using a larger Time Window Size raises the Effective Rate Limit Request Count, which means more requests are needed to trigger rate limiting. | ||
|
Change the Rate Limit and Delta values above to see how the Effective Rate Limit Request Count ranges change below for each Time Window based on its size and error boundaries. If the Delta value is set to 0, no ranges will display. |
||