There's really not much tuning that can be done in regard to AWT's. You can change the number of them and you can also reserve some to be used for "quick-running" queries (PI or USI type accesses). You would only want to make these changes after consulting with NCR support though.
The only time AWT's become a problem is if you have too much work running against your machine at one time and you are running out of AWT's. There are 80 AWT's allocated per AMP by default. You run into issues once 62 of them are being used and additional work is being submitted to the machine. As you approach 62 AWT's that are being used, this indicates that you should control the amount of work being submitted through the use of TDWM or some other facility that limits the number of simulataneous queries/utilities that can run at any one time.
The "puma -c" console command will let you know how many AWT's are active. You need to add up the "Inuse" column for an AMP to see how many AWT's are active on that particular AMP.