While I was reading the Splunk documentation about "Configure the priority of scheduled searches" linked at Configure the priority of scheduled searches,
I came across "Example of real-time scheduling versus continuous scheduling" linked at Configure the priority of scheduled searches
And I am wondering if our happy Splunkers can analyze this section in how search scheduler controls with multiple of scheduled saved searches being queued up and dispatched / run or etc in sort of waiting queue with respect to option values like run_time, dispatch_time and scheduled_time in savedsearches.conf.
Given scheduled_time, dispatched_time, and run_time, and you have already read the example of real-time scheduling versus continuous scheduling linked at e.g. of real-time vs. continuous scheduling, I would like to know the following things:
(a) At which point can"dispatched_time" be verified ?
(b) At which point can "run_time" be verified ?
(c) At which point can "scheduled_time" be verified ?
Perhaps, you could explain fully by drawing a figure such as the Gantt Chart for the scheduled saved searches.
Sidenote: FYI, we draw Gantt Chart when understanding how the CPU processes arrive in the QUEUE in order, what the waiting time is, or etc when it comes to CPU scheduling algorithms in the filed of operating systems.
Any explainations?