Discovery scan duration impacted by ServiceNow instance

[ronlucas]

Running Istanbul...

Yesterday, when I had several discovery jobs running, I tried to perform another discovery of a single IP address of a Windows computer.   This usually takes less than 2 minutes, but it took over an hour to complete.   Then I noticed the "Scheduler queue length" seen in System Diagnostics was as high as 180 on 4 out of 8 ServiceNow cluster nodes.   After the scheduled discovery scans were complete, I ran another discovery of the single IP address again, and it finished within 2 minutes as expected.

So it would appear that the total duration of a discovery job is impacted not only by settings on MID servers (threads, java memory, etc), but also the load on the ServiceNow instance.

Can someone confirm this?  

Thanks.

[Dave Ainsworth]

Hi Ron,

If you are admin and have the default homepage, you will see something like the following:

The Discovery set will give you all the graphs you need and then you can select node, time span etc.

The other way you are suggesting above I don't think gives you as much control.