High Memory usage for Windows Internal Database with WSUS on server 2012

I have recently configured a 2012 Vmware instance to be my WSUS server.  I am noticing that it is not running properly and the CPU and the Memory for the Windows Internal Database are spiking.  Is there some tuning I need to do with the windows internal database to make this function better?  Is there a recommended minimum vCPUs and vMemory for this product?
DwciAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

arnoldCommented:
How many clients does the wsus servername and what is your detection setting inGPO set to?mi.e. How often is the client configured to check for updates. Once a day is enough .
What else if anything does the system do?
Minimum memory for Windows 2012, how many products/classifications did you choose?
DwciAuthor Commented:
125 clients, checks once a day, minimal other things.  The big problem I see is the spike in the internal database and then it stays up.  I have 8GB of memory and 4 CPU's in use so I think the server is not the problem.
Seth SimmonsSr. Systems AdministratorCommented:
when does the cpu spike?
with 125 clients, you shouldn't need 4 cpu; 1 should be enough
memory usage is not unusual; anything exchange or sql related (WID is basically sql embedded) will normally use a lot of memory
Protecting & Securing Your Critical Data

Considering 93 percent of companies file for bankruptcy within 12 months of a disaster that blocked access to their data for 10 days or more, planning for the worst is just smart business. Learn how Acronis Backup integrates security at every stage

FREE DOWNLOAD
DwciAuthor Commented:
If I restart the windows internal database service, then go into WSUS console and when it tries update the summary the processor goes to 1/2 used and then the memory starts to grow that is being used by the internal database..  I also have another task that is showing a steady 600+MB of memory "IIS Worker Process".  Sometimes the console will time out and allow me to "reset the node".
Seth SimmonsSr. Systems AdministratorCommented:
not unusual; my servers do the same thing
i have 110 clients and the IIS memory usage is 720mb and WID 760mb
typically when mmc says the console timed out is because of a long running process such as a cleanup wizard
i would check the application log to see if any services are stating that it isn't working properly
arnoldCommented:
Wid will use as much memory is available up to the size of the DB
On service restart, the CPU spike deals with wid requesting memory allocation.
A memory spike needs to be defined do you see each vCPU individually or do you have a single representation?
from 50 to 60 %
From 10 to 30%
Etc.
When are the clients set to check. Do all clients turned off at night and are set to check for updates if scheduled is missed?

This would explain if all are turned on at 7 and you see this issue from 7 until about noon.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2012

From novice to tech pro — start learning today.