asked
when to configure max worker threads away form default
Hello all, Trying to determine if thread starvation is an issue on a server with sluggish response or when to change the default max worker thread setting. select scheduler_id,current_tasks_count, current_workers_count,active_workers_count,work_queue_count from sys.dm_o[link text][1]s_schedulers where status = 'Visible Online' per this link
http://blogs.msdn.com/b/sql_pfe_blog/archive/2013/07/01/are-my-actual-worker-threads-exceeding-the-sp-configure-max-worker-threads-value.aspx not all the threads are counted against max worker threads. The following to me seems too simple when select Count(*) from sys.dm_os_threads > select max_workers_count from sys.dm_os_sys_info Not trying to overcomplicate a simple process but trying to expand my knowledge. TIA, Joe [1]:
http://blogs.msdn.com/b/sql_pfe_blog/archive/2013/07/01/are-my-actual-worker-threads-exceeding-the-sp-configure-max-worker-threads-value.aspx
I've never done it. I'd say leave it at the defaults unless you absolutely know you have an issue. Further, it's unlikely that you have a thread issue unless you're running things like Availability Groups or Service Broker. So, until you get there, focus on other areas. Thread management is WAY down my list of concerns on the majority of servers I've worked on or consulted on. But, if you're seeing queueing in areas that are likely to be thread specific, then you might consider checking further.
16 People are following this question.
