16.20 - Strategy 2 - Parallel Transporter

Teradata® Parallel Transporter User Guide

Product
Parallel Transporter
Release Number
16.20
Published
August 2020
Language
English (United States)
Last Update
2020-08-27
dita:mapPath
uah1527114222342.ditamap
dita:ditavalPath
Audience_PDF_product_tpt_userguide_include.ditaval

Start with MaxSessions equal to the number of available AMPs or number of sessions allocated for the job, using four instances of each operator (producers and consumer).

  1. Run the job and examine the output:
    • How long did it take for the job to complete?
    • How many consumer operator instances are being used?
    • How many rows are being processed by each consumer operator instance? We are looking for balance without wasted resources.
  2. Make adjustments based on your results.
    • If the job is not using all the consumer operator instances:

      Decrease the number of instances to eliminate the unused ones.

      Decrease the number of producer instances by one. Avoid doing anything too drastic, or it will be difficult to determine the optimal number.

    • If the job is using all the consumer operator instances, and the workload is balanced, try increasing the number of consumer operator instances.
    • If the job is using all the consumer operator instances, but the workload not balanced, try increasing the number of producer operator instances.
  3. Rerun the job and compare the output:
    • Did the job run faster? Remember, this is the ultimate goal!
    • Was there a change in the number of consumer operator instances used?
    • Was there a change in the balance of data in the consumer operator instances?
  4. Repeat the process to optimize the number of producer and consumer instances.

Now that you know the best number of instances, you can modify the number of MaxSessions to see if there is an impact.

  1. Decrease the number of MaxSessions. It is best to make MaxSessions a multiple of the number of instances for the operator so they are evenly balanced across the instances.
  2. Rerun the job and compare the output:
    • Did the job run faster?
    • Was there a change in the number of consumer operator instances used?
    • Was there a change in the balance of data in the consumer operator instances?
  3. Depending on the results, you may want to use the original MaxSessions, or continue experimenting. You may even want to re-visit the number of instances you are using.