How to Calculate Your Max Number of Usable AMP Worker Tasks - comment by carrie

Hi Ana,
 
Releasing COD will not increase the number of AMP worker tasks to your platform, but it will increase CPU and I/O resources, so requests that are holding AWTs should be able to complete sooner, release their AWT sooner, and allow AWTs to be available for other work sooner.  I would expect you would see lower AWT usage levels with more processing power available if the active work running on the platform is the same.
 
It is not necessarily problematic to have more than 62 AWTs active at the same time (assuming you have the default of 80 AWTs/AMP defined).  As long as a delay in getting an AWT for some of the requests is not causing problems meeting a response time goals.  However, if you are reaching 62 in-use AWTs from time to time, it is an indication that you are begininng to run out of AWTs, so workload management throttles are usually a good idea to consider, if you haven't already.  If yo use throttle rules, you can decide which workloads you want to experience a wait at busy times (by means of a throttle delay queue), rather than having it be randomly determined which queries will have their work messages wait in the work message queue.
 
Thanks, -Carrie