Optimizing Teradata Requests with Group-AMP Operations for Improved Performance

All-AMP and single-AMP operations are well-understood. All-AMP retrieval typically involves full table scans, including NUSI sub-table scans. On the other hand, single-AMP retrieval typically involves indexed access, such as UPI and NUPI.

Group-AMP operations optimize requests by minimizing the number of active AMPs. These operations fall between single-AMP and all-AMP operations. The Optimizer employs group-AMP for data retrieval and joins.

Various factors contribute to enhanced performance in the Group-AMP operation. Unlike the all-AMP operation, Group-AMP eliminates the need for table locks and enables the Optimizer to utilize row hash locks for the relevant rows instead.

Using row hash locking substantially reduces the likelihood of simultaneous execution of insert and update statements resulting in blockage.

Group-AMP operations eliminate the need for the table lock/release steps required at the start and end of a request in all-AMP operations.

When will the Optimizer use Teradata Group AMP Operations?

Group-AMP operations rely on the Optimizer’s capacity to identify request steps that consume less than half of the available AMPs. For instance, group-AMP is only utilized in a system with 100 AMPs if no more than 50 AMPs are necessary to retrieve data. The collection of statistics significantly aids the Optimizer in approximating the number of implicated AMPs. In the absence of statistics, the probability of the Optimizer utilizing group-AMP is minimal.

Teradata must adhere to the following usage criteria: the execution plan must be driven by either a single-AMP step or a group-AMP step. Since NUSI access is always an all-AMP operation, it cannot be the first phase of the execution plan when group-AMP access is utilized. Additionally, group-AMP access cannot be used when a product join step with data relocation is based on table duplication.

Group-AMP, OLTP, and Tactical Workload

Group-AMP operations can improve OLTP and tactical workloads by employing rowhash-level locks on fewer AMPs, increasing read and update concurrency compared to all-AMP operations. It is worth noting that the benefits of group-AMP operations become more significant as the number of AMPs in the system increases.

Related Services

⚡ Need Help Optimizing Your Data Platform?

We cut data platform costs by 30–60% without hardware changes. 25+ years of hands-on tuning experience.

Explore Our Services →

📋 Considering a Move From Teradata?

Get a personalized migration roadmap in 2 minutes. We have migrated billions of rows from Teradata to Snowflake, Databricks, and more.

Free Migration Assessment →

📊 Data Platform Migration Survey

Help us map where the industry is heading. Results are public — see what others chose.

1. What is your current data platform?

2. Where are you migrating to (or evaluating)?

Migrating FROM
Migrating TO

Thanks for voting! Share this with your network.

Follow me on LinkedIn for daily insights on data warehousing and platform migrations.

Stay Ahead in Data Warehousing

Get expert insights on Teradata, Snowflake, BigQuery, Databricks, Microsoft Fabric, and modern data architecture — delivered to your inbox.

Leave a Comment

DWHPro

Expert network for enterprise data platforms. Senior consultants, project teams built for your challenge — across Teradata, Snowflake, Databricks, and more.

📍Vienna, Austria & Jacksonville, Florida

Quick Links
Services Team Teradata Book Blog Contact Us
Connect
LinkedIn → [email protected]
Newsletter

Join 4,000+ data professionals.
Weekly insights on Teradata, Snowflake & data architecture.