the problem I am trying to troubleshoot is concerned with a dashboard that displays reliability statistics over a given period. Unfortunately it displays a red light as soon as a poison wait threshold is reached and in this case the wait was THREADPOOL.
Although performance is ok, we are beginning to express concern that as the environment grows, inefficient SQL will compound the problem. In end effect I am trying to proactively anticipate a potential problem and resolve it before I have to post an emergency HEEEELLLLPPPPP here!
From what Uwe has explained, reducing the size of the execution plan (at least the expensive components that need to be parallelised) might help. The next step from my side is to identify the most expensive plans and try to optimise them. Because the MAXDOP is only going to be applied to threads that need to be parallelised I am going to suggest raising the threshold of parallelism and reduce the MAXDOP.
It could be interesting....