[Aces-support] walltime question

[aces-admin at techsquare.com]

hello hiyao-

i believe that you may be over-thinking this. 

your job, for example, does not take any longer
to run when executed in the 'long' queue than 
when executed in the 'one' queue 

  unless your job does not terminate and you 
  simply wait for the queue-system to beat it 
  up. in this case, you should write some terminal
  conditions to your job.

what you may notice, however, is that jobs in
the 'one' queue are scheduled more readily than
jobs in the 'long' queue. this has more to do 
with the default resource requirements for each
queue and you should be able to achieve similar
scheduling results by submitting your job to the
'long' queue and requesting only 12h of walltime.

  qsub -q long -l nodes=1,walltime=12:00:00

did i mis-read your message entirely or is this
'on the right track' ? 

[greg]




> Date: Tue, 02 Dec 2008 10:25:46 -0500
> From: Huajian Yao <hjyao at mit.edu>
> MIME-Version: 1.0
> Cc: 
> Reply-To: ACES-support at mitgcm.org
> 
> Hi,
> 
> I am running (many) jobs each with single node one cpu on the cluster. The
> computation
> time usually takes about 9-12 hours for each job. Usually I run my code using
> "long" job which works pretty well but takes too much time. I have heard from
> someone that the walltime for "one" type job has changed to 12 hours. However,
> on
> the acesgrid.org, the walltime for "one" is still 2 hours. Yesterday I tried
> some "one" type jobs on the cluster but all killed after about 6 hours. Could
> you
> please let me what is the real walltime for "one" type job? Thanks a lot!
> And I really hope the walltime for "one" can extend to 12 hours.
> 
> Huajian
> _______________________________________________
> Aces-support mailing list
> Aces-support at acesgrid.org
> http://acesgrid.org/mailman/listinfo/aces-support
>