Archives of the TeradataForum
Message Posted: Mon, 14 Jun 2004 @ 17:41:09 GMT
| Subj: | | Re: AMP worker tasks |
| |
| From: | | Robert D Meunier |
I've been at sites where this number has been increased and have heard of additional sites where it's been increased. As I understand it this
is one of those things where NCR does not recommend that the customer change this number unless they've previously consulted (in length) with
NCR.
What I've seen (and heard) is that increasing this number can sometimes alleviate running short on AWTs. However, what I've seen as a
consequence is that some other resource becomes the bottleneck and the net gain is questionable. Remember, if you raise the number from 80 to 100
you now have 25% more AWTs all requesting resources (CPU and I/O) from what is a limited pool. You might be able to have more active processes,
but they are all going to get a thinner slice of the resources.
Work Flow management has always been toted as the overall solution to situations where AWTs have become the bottleneck.
As an aside, I've also been to a site where the number was decreased from 80 to 60, though I don't know what the rationale was for this.
Robert Meunier
| 
