(Click to open topic with navigation)
This command displays the estimated start time of a job based a number of analysis types. This analysis may include information based on historical usage, earliest available reservable resources, and priority based backlog analysis. Each type of analysis will provide somewhat different estimates based on current cluster environmental conditions. By default, only reservation based analysis is performed.
The start time estimate Moab returns does not account for resources that will become available due to preemption.
Historical analysis utilizes historical queue
times for jobs which match a similar processor count and job duration profile. This
information is updated on a sliding window which is configurable within
Reservation based start time estimation incorporates information regarding current administrative, user, and job reservations to determine the earliest time the specified job could allocate the needed resources and start running. In essence, this estimate will indicate the earliest time the job would start assuming this job was the highest priority job in the queue.
Priority based job start analysis determines when the queried job would fit in the queue and determines the estimated amount of time required to complete the jobs which are currently running or scheduled to run before this job can start.
In all cases, if the job is running, this command will return the time the job started. If the job already has a reservation, this command will return the start time of the reservation.
By default, this command can be run by any user.
|--blocking||Do not use cache information in the output. The --blocking flag retrieves results exclusively from the scheduler.|
|DURATION||Duration of pseudo-job to be checked in format [[[DD:]HH:]MM:]SS (default duration is 1 second)|
|-e||Estimate method. By default, Moab will use the reservation based estimation method.|
|-f||Use feedback. If specified, Moab will apply historical accuracy information to Improve the quality of the estimate.|
|-g||Grid mode. Obtain showstart information from remote resource managers. If -g is
not used and Moab determines that job is already migrated, Moab obtains showstart
information from the remote Moab where the job was migrated to. All resource
managers can be queried by using the keyword "all" which returns all information
in a table.
$ showstart -g all head.1 Estimated Start Times [ Remote RM ] [ Reservation ] [ Priority ] [ Historical ] [ c1 ] [ 00:15:35 ] [ ] [ ] [ c2 ] [ 3:15:38 ] [ ] [ ]
|-l qos=<QOS>||Specifies what QOS the job must start under, using the same syntax as the msub command. Currently, no other resource manager extensions are supported. This flag only applies to hypothetical jobs by using the proccount[@duration] syntax.|
Displays verbose information.
|JOBID||Job to be checked|
|PROCCOUNT||Number of processors in pseudo-job to be checked|
|S3JOBSPEC||XML describing the job according to the Dept. of Energy Scalable Systems Software/S3 job specification.|
> showstart orion.13762 job orion.13762 requires 2 procs for 0:33:20 Estimated Rsv based start in 1:04:55 on Fri Jul 15 12:53:40 Estimated Rsv based completion in 2:44:55 on Fri Jul 15 14:33:40 Estimated Priority based start in 5:14:55 on Fri Jul 15 17:03:40 Estimated Priority based completion in 6:54:55 on Fri Jul 15 18:43:40 Estimated Historical based start in 00:00:00 on Fri Jul 15 11:48:45 Estimated Historical based completion in 1:40:00 on Fri Jul 15 13:28:45 Best Partition: fast
> showstart 12@3600 job 12@3600 requires 12 procs for 1:00:00 Earliest start in 00:01:39 on Wed Aug 31 16:30:45 Earliest completion in 1:01:39 on Wed Aug 31 17:30:45 Best Partition: 32Bit
You cannot specify job flags when running showstart, and since a job by default can only run on one partition, showstart fails when querying for a job requiring more nodes than the largest partition available.
3.44.6 Additional Information
For reservation based estimates, the information provided by this command is more highly accurate if the job is highest priority, if the job has a reservation, or if the majority of the jobs which are of higher priority have reservations. Consequently, sites wishing to make decisions based on this information may want to consider using the RESERVATIONDEPTH parameter to increase the number of priority based reservations. This can be set so that most or even all idle jobs receive priority reservations and make the results of this command generally useful. The only caution of this approach is that increasing the RESERVATIONDEPTH parameter more tightly constrains the decisions of the scheduler and may resulting in slightly lower system utilization (typically less than 8% reduction).