Increasing max run time for discovery schedule

[chowdhary]

Hi All,

Will there be any performance impact in case if we increase the "Max run time" for discovery schedules?

[anurag92]

Probably not, but it's better to keep a limit on it. In my previous organization, a   Discovery expert once told me.. how 1 Discovery schedule messed up at network end. Due to some issue at Client-network end, Discovery ran for around 11 hours. This caused various spikes at client end and they were unable to find the reason for long. Luckily, ServiceNow people were engaged and were able to find the cause. So, it might not cause performance issues. It it very likely that 95% of times, Discovery will complete on time. However, to handle 5% cases which can be seriously impacting,   it's better to have a max run time.

[chowdhary]

Thanks a lot Anurag for the information.

[doug_schulze]

Max run time was put in so long ago for a friend of mine who needed his schedules to stop at the end of their change window (which was @ 4am) and he didn't want to wake up to do so.   I advised that he needed to add more resources (more mids) because his goal should be to complete in the allotted time of his change window, that is the best practice.

As we progressed the max run time helped for a short period before they finally just modified the change process to allow discovery to run as is.. So ironically he never really got much use out of it..

I would suggest not to rely on Max Run time to stop your schedules.. give them the resources needed to finish in the time you need them to. Not to say its a bad thing to use it, some folks out there use it as a safety catch for schedule completion, which works!   But do understand that the next time that schedule runs it starts from the beginning and will NOT start where the Max run time canceled it previously...  

[chowdhary]

Thanks a lot Doug for sharing very useful information.

Best Regards

Chowdhary