Request Throttles | Teradata Vantage - Request Throttles - Analytics Database - Teradata Workload Management

Teradata Vantageā„¢ - Workload Management User Guide - 17.20

Deployment
VantageCloud
VantageCore
Edition
Enterprise
IntelliFlex
VMware
Product
Analytics Database
Teradata Workload Management
Release Number
17.20
Published
June 2022
Language
English (United States)
Last Update
2023-01-27
dita:mapPath
aji1628112479055.ditamap
dita:ditavalPath
qkf1628213546010.ditaval
dita:id
B035-1197
Product Category
Teradata Vantage

The most popular use of throttles is to limit concurrent requests. When you enable a throttle rule, TASM counts the active requests the rule applies to. When a new request is ready to run, TASM compares the request count with the rule limit. If the count is below the limit, the request runs immediately. If the count is equal to or above the limit, TASM either rejects the request or puts it in a delay queue. Most throttles delay requests rather than reject them.

When system activity falls below the throttle limit, the system runs delayed requests in the order you select for releasing the throttle delay queue:
  • By time delayed: The requests delayed the longest are released first
  • By workload priority: The request from the highest-priority workload is released first
The Order the Throttle Delay Queue option is available in the General area of Viewpoint Workload Designer on the Other tab.

If a delayed request starts to run, it cannot be delayed again.

If a request is subject to multiple throttles, all throttles must be below the limit before the request can run.