ServiceNow Discovery spiking CPU usage to 100% on VM

lileem09
Kilo Expert

Is anyone experiencing issues with Discovery spiking the CPU usage to 100% on a VM?

8 REPLIES 8

manikorada
ServiceNow Employee
ServiceNow Employee

There might be a specific Payload which might be using all the resources. I would suggest to check the Midserver logs and see when the spike is happening and at that time what is discovery doing.


doug_schulze
ServiceNow Employee
ServiceNow Employee

Melinda,


indeed it can and usually does happen.. Java loves it some CPU and Memory.. I had a friend who was the discovery and VM Admin.. so on a slow afternoon we cranked up the java threads to 300 to see what would happen and how much CPU was needed before it wasn't a problem.. 16 quad core CPU's and 8 Gig of Ram did the trick, it hovered at 60% utilization..



Bottom line, you are going to see 100% utilization regardless.. as long as you aren't seeing it stay at 100% from start to finish you should be fine.. Now if you are, well its hungry and needs more resources!



Hope this helps and if you would like you can PM me and we talk more and maybe look at it together!



-Doug


Doug,


  I need to add a little more clarification about what Melinda asked about. The VM was the target being scanned, not the MID server. While I can expect 100% utilization of a MID server, I'm curious about what happens on the target being scanned. Based on the everything I've seen, can we assume that there is nothing that will prevent a target server from using all of its resources during a scan?



John


100% CPU utilization is expected on MID but not the targets being scanned. It uses remote wmi queries. Even though, some resources would be used to respond. Are you seeing targets with spiked CPU?