17.10 - When to Use a Virtual Partition Throttle - Advanced SQL Engine - Teradata Workload Management

Teradata Vantageā„¢ - Workload Management User Guide

Advanced SQL Engine
Teradata Workload Management
Release Number
Release Date
July 2021
Content Type
User Guide
Publication ID
English (United States)
Use virtual partition throttles only as needed, and keep the TASM setup as simple as possible. Here are some situations in which virtual partition throttles can be useful:
  • Multi-tenant architecture: Use virtual partitions to separate companies (tenants) who share a Teradata platform. In this situation, it is important to have strong use limits. Adding a virtual partition throttle ensures that one tenant cannot monopolize AMP worker tasks or other resources. When you set the throttle limit, consider the type of requests the tenant runs and how many AMP worker tasks their requests typically use (usually 1 to 4).
  • Geographic or business unit separation: Virtual partitions are also useful when you need to separate business units or geographic locales. In this case, a virtual partition throttle may not be necessary. However, if there is a shortage of AMP worker tasks and if their use is not balanced evenly between virtual partitions, virtual partition throttles can help share resources more fairly.

When you are setting a virtual partition throttle limit, consider the type of work involved. If the work is dominated by complex requests with frequent parallel steps and redistributions or by many concurrent load jobs, a lower throttle limit may be needed. Consider a higher throttle limit for virtual partitions that do shorter, simpler work.