On Thu, 2007-11-29 at 14:20 -0500, Steve Young wrote:
> I just noticed this and wanted to post to see if this still an issue
> or perhaps it has been fixed now.
>> I don't use it very much but I was using the showstart command to
> look at a couple jobs to see when they might be done running. First
> let me explain how the jobs are set up. A user has like 30 jobs in
> the queue. All of them are set up to go to one specific machine using
> the #PBS -l host=<machinename> directive. Each job is running for 500
> hours so it might be some time before they are all finished. Anyhow,
> I ran the showstart command on the first idle job in the showq list
> and the last idle job in the showq list. Here is the output:
>> [root at jake ~]# showstart 48542
> job 48542 requires 2 procs for 20:20:00:00
> Earliest start in 20:09:26:14 on Wed Dec 19 23:26:38
> Earliest completion in 41:05:26:14 on Wed Jan 9 19:26:38
> Best Partition: DEFAULT
>> [root at jake ~]# showstart 48574
> job 48574 requires 2 procs for 20:20:00:00
> Earliest start in 20:09:26:14 on Wed Dec 19 23:26:38
> Earliest completion in 41:05:26:14 on Wed Jan 9 19:26:38
> Best Partition: DEFAULT
>> Both jobs show the same dates. So it would appear to me that
> showstart can't really predict when the job can run. It can only
> predict when the next job will be able to run? Anyone run into this
> before? Thanks,
Exactly, showstart gives you an estimate of the "Earliest start" for the
job. It doesn't try to predict the future :-)
Trying to predict the actual start time is an almost impossible task.
--
Ake Sandgren, HPC2N, Umea University, S-90187 Umea, Sweden
Internet: ake at hpc2n.umu.se Phone: +46 90 7866134 Fax: +46 90 7866126
Mobile: +46 70 7716134 WWW: http://www.hpc2n.umu.se