Archives of the TeradataForum
Message Posted: Mon, 14 Jun 2004 @ 21:13:45 GMT
| Subj: || || Re: AMP worker tasks |
| From: || || Walter, Todd A |
Being out of AMP worker tasks is not bad by itself. Teradata is designed to queue up steps for which there is no available AMT at this moment
and to consume that queue in priority order as other work finishes. It is rare that 80 AWTs leave an CPU or I/O processing capability on the
table, this is the goal - run enough steps concurrently to utilize all the machine resources without over-sharing those resources.
In general, the only reason to increase AWTs is if the workload is such that all AWTs are full and the system is not running at full
utilization. This has proven to be possible but is rare. If the system is fully utilized when AWTs are full, then the system is just maxed out and
other actions are indicated: optimization, workload management/smoothing, more capacity,...
As was stated by others - consult withGSC on the particulars of your system before making this change. Older systems with less physical memory
may not find it advisable at all for instance. And any site making the change may need to change other parameters (eg FsgCache%) before doing