So I have installed a new instance of WSUS on a 2012R2 system. The WSUS server will be serving about 350 systems (servers+desktops+laptops) total. It is running in a Hyper-V VM, and I currently have allocated it 10GB of memory, but in less than a day the Windows Internal Database usage has jumped up to about 6GB.
This value seems excessive to me. If you search Google you can find tons of articles on how to limit the memory for the Windows internal database. But almost none of the articles I am finding provide any rationale why the chose a particular memory value which seems be between 256MB-4GB depending on the author of the article.
Is this memory usage for WSUS normal? I am not finding any official Microsoft sizing suggestions for WSUS on 2012r2, though docs for an older release suggests that 1GB should be enough for less than 500 computers.
So my question are
- Is there update location Microsoft has published server sizing specs for WSUS that I am not finding?
- If I were to set a memory limit for the internal database, what method should be used to pick the right value? Is there some formula, or some performance metric I can look at to set a useful limit?
- Do I just need to keep adding more memory until WSUS stops using it all?
- Is there something else I should be doing instead to make WSUS use less resources?