Archives of the TeradataForum
Message Posted: Wed, 25 Sep 2002 @ 15:59:25 GMT
The problem is that amp worker tasks (now) run at the same priority (work allocation group setting) as the work they are supporting. You only get 60 per amp worker tasks before you run into flow control (you run out). Each utility and/or heavy duty sql takes so many amp worker tasks. There is a formula for what uses how many amp worker tasks.
We are in the process of setting up work allocation groups for managing the distribution of CPU. But that is a long involved process and this is somewhat of a different issue.
When you are out of amp worker tasks, you do not run at 100% CPU. Amp Worker Tasks become a resource constraint which is a separate issue from priority scheduler which would control CPU allocation for work groups. You cannot use all the CPU when you are in flow control.
All I hope to accomplish is to throttle down new work coming onto the system until the system is not saturated or prevent it from getting saturated.
|Copyright 2016 - All Rights Reserved|
|Last Modified: 27 Dec 2016|