Request Throttles | Teradata Vantage - 17.10 - Request Throttles - Advanced SQL Engine - Teradata Workload Management

Teradata Vantageā„¢ - Workload Management User Guide

Product
Advanced SQL Engine
Teradata Workload Management
Release Number
17.10
Release Date
July 2021
Content Type
Administration
User Guide
Publication ID
B035-1197-171K
Language
English (United States)

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 execute, 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.