16.10 - Workload Throttles - Teradata Workload Management

Teradata Database Workload Management User Guide

Teradata Workload Management
June 2017
User Guide

TASM rejects or delays requests controlled by workload throttles.

Because workload throttles are predictable and easy to understand, Teradata recommends them as the main tool for limiting work on a busy system. Workload throttles are easier to monitor and make it easier to assess request delay times. It is also clearer which requests are affected by workload throttles. A system throttle often needs complex criteria to achieve the same scope as a workload throttle. This complexity can add confusion when analyzing throttle behavior and the impact of delays.

If SQL requests in a stored procedure classify to a throttled workload, TASM throttles the requests in the procedure individually.

Workload throttles work well when a hardware component is down, and the system is running in degraded mode. The administrator can reduce the throttle limit for low-priority workloads so that high-priority workloads can still deliver consistent response times.