 |
 |
Archives of the TeradataForum
Message Posted: Fri, 08 Aug 2003 @ 20:02:26 GMT
| Subj: | | Re: Process awtmain |
| |
| From: | | Adriano Rodrigues Ferreira |
Thanks to Dieter and Otto (who pointed me an article at Teradata knowledge base).
| | > I see around 850 processes and approximately 480 processes /tpasw/bin/awtmain. Am I in trouble? Is this expected, isn't? | |
| | Don't worry, it is expected ;-) Awtmain is the "AMP worker task", the working unit in Teradata doing the different steps you see in
Explain, 1 AWT per step. There are 80 AWTs per AMP, so you probably run a 6 AMP system. | |
You are absolutely right. This is a 6 AMP system which is giving me some hard time investigating possible causes to its poor
performance. I thought that maybe it could be due to some malfunction related to a large number of unnecessary processes running. With your
answers, this is obviously not the case. When idle, this machine is showing up a CPU usage rate of 10% user time and 40% system time that I
can't explain.
Thanks for the (amazingly fast) answers.
| | > I would like to learn something about the diverse processes of the Teradata database like awtmain, pardrivr, disworkt. I
would appreciate if someone give me pointers about what to expect to be running at the Teradata server. | |
| | I don't know exactly about those processes and AFAIK there's no whitepaper/manual on that. Maybe Todd Walter could shed some light
on it ;-) | |
I continue to look for clues that tell me that either something is working bad at the system (wasting CPU) or that I have some
configuration problem. If anyone has a hint on this kind of problems, I would be very grateful.
Below is a typical output of the sar Unix utility for CPU usage.
18:32:31 %usr %sys %wio %idle
18:32:41 10 39 0 51
Regards,
Adriano.
| |
