About Increasing the Number of Agents - Teradata Data Mover

Teradata Data Mover User Guide

Product
Teradata Data Mover
Release Number
16.00
Published
December 2016
Language
English (United States)
Last Update
2018-03-29
dita:mapPath
rdo1467305237457.ditamap
dita:ditavalPath
ft:empty
dita:id
B035-4101
lifecycle
previous
Product Category
Analytical Ecosystem

Each agent is capable of processing five tasks at one time. Increasing the number of agents allows more tasks to be processed at one time, increasing the number of Data Mover jobs processed at one time. In some cases, this improves individual Data Mover job performance.

Data Mover jobs that use Teradata PT API or Teradata JDBC have separate tasks for each table being copied. Increasing the number of agents improves the job performance by allowing more of the job tables to be copied concurrently.

Data Mover jobs that use Teradata ARC do not have separate tasks for each table being copied. In this case, increasing the number of agents does not allow more of the job to run in parallel; however, job performance could improve if the job was previously competing with other jobs for resources.

You may also want to limit the maximum number of current tasks that an agent can run by setting the agent.maxConcurrentTasks parameter in the agent.properties file. This parameter is set dynamically and does not require that the agent service be restarted. If you update the value, it takes effect one minute after the updated file is saved. In addition, you can also use flexible scheduling to set different concurrent limits depending on the time of the day.