Well size differs, but for us we did 10000 and 8. That was old R2. We haven't touched the 2012 boxes and won't until we see IIS crack.
_________________ Brian Mason MCTS, MS MVP ECM <http://www.mnscug.org/> http://www.mnscug.org/ From: [email protected] [mailto:[email protected]] On Behalf Of Sam George Sent: Monday, July 1, 2013 12:34 PM To: [email protected] Subject: RE: [mssms] WSUS Scan issue What's the setting you set for the Queue Length and Max worker Processes? /SAM _____ From: [email protected] <mailto:[email protected]> To: [email protected] <mailto:[email protected]> Subject: RE: [mssms] WSUS Scan issue Date: Mon, 1 Jul 2013 11:59:21 -0500 We pushed a few SUPs too hard. I know they got to around 37K clients each before they started showing symptoms like you're having (IIS 7.5). One thing we did was to up the Queue Length and Max Worker Processes for the WSUS Pool. But that only helped a tad. It's yet to be seen how far IIS 8 can go for a super heavy SUP load. _________________ Brian Mason MCTS, MS MVP ECM <http://www.mnscug.org/> http://www.mnscug.org/ From: [email protected] <mailto:[email protected]> [mailto:[email protected]] On Behalf Of Sam George Sent: Monday, July 1, 2013 12:54 AM To: [email protected] <mailto:[email protected]> Subject: [mssms] WSUS Scan issue Hi All, For the past few days we are seeing a strange issue with WSUS Scan when clients are trying to SCAN against the WSUS server, connections are dropping at WSUS pool level and clients are resetting the connection . When we investigated the issue, found that the connections are accumulating at worker process leave and WSUS pool is unable to process them due to latency in processing the request. To remediate this, as a workaround we have added the MaxConcurrentRequestsPerCPU registry key and set the value to 5000 to increase the Concurrent Requests. This is helping to process the requests but servers are consuming the memory and server performance is degraded. We have three servers in NLB and we are supporting approx 50K clients with these three SUP servers. We tried to remove one server from NLB thinking it was something to do with NLB but that too did not help. We have tried to eliminate corruptions in IIS or WSUS by uninstalling the IIS and WSUS on one server but still we are seeing same issue (we have two servers behind NLB and both are behaving in same way). Can someone give us some pointers where to look what might be the reason for WSUS pool to take long time to process the request and how we can fix this issue. Appreciate your help. Below is the connection drop error from http error log . POST /SimpleAuthWebService/SimpleAuth.asmx Windows-Update-Agent - - testlab.com - 0 880 59386 1 Connection_Dropped_List_Full WsusPool Regards, /SAM
