WSUS on Server 2016 - Hogging the CPU!

[FN-GM]

Hello,

 

I have moved SCCM onto Server 2016. The SCCM bit went fairly well.

 

The big issue I have is WSUS is tanning the CPU and using 100% of it when I do synchronization. It in the task manager as IIS Work Process, eventually the IIS Application Pool will crash and then WSUS doesn't function at all. No matter how many cores I give the VM it doesn't make a difference.

 

I have been various suggestions that suggest changes in the application pool in IIS, but nothing seems to work.

 

Does anyone have any suggestions please?

 

Thanks

Edited April 24, 2017 by FN-GM

[mukz]

Maybe this might help?

 

https://www.windows-noob.com/forums/topic/15028-primary-site-server-high-cpu-usage-iis-worker-process-for-wsuspool/

[FN-GM]

Doesn't make a difference

[computer_expert]

Is WSUS configured to use the internal DB or SQL? Have you checked the memory limits for the WID/SQL Server?

[FN-GM]

The problem went and has come back. Now it is using all my RAM as well. It was using nearly 30GB RAM!

[HPlum78]

https://blogs.technet.microsoft.com/configurationmgr/2017/08/18/high-cpuhigh-memory-in-wsus-following-update-tuesdays/

[Duke5A]

This may or may not be related: I just stood up a WSUS instance on Server 2016 and had the application pool crash often. This was with factory fresh settings. Server is physical with eight cores and 16GB of RAM and the only other thing that runs on it is WDS. I eventually found this was able to cure the pool crashing constantly.

 

https://blogs.msdn.microsoft.com/the_secure_infrastructure_guy/2015/09/02/windows-server-2012-r2-wsus-issue-clients-cause-the-wsus-app-pool-to-become-unresponsive-with-http-503/