[Swift-devel] Walltime in PBS submit files

[Mihael Hategan]

Oops. The email server certificate changed and I didn't notice it until
today. So sorry for the late reply.

The maxTime parameter is there to enforce queue constrains so that
blocks don't trip over those. The blocks also consider some margin of
error when scheduling jobs. This is currently 30 seconds. So the maximum
possible walltime for a job will be maxTime - 30s. Even if that was not
the case, you would still not be able to fit a job with a walltime of
maxTime, since some seconds are lost between the time a worker is
started and the time a job is actually sent to that worker.

So you should understand maxTime as "never submit blocks larger than
this time".

On Fri, 2011-06-03 at 10:21 -0500, Tim Armstrong wrote:
> I'd been trying separately to understand the effect of the maxTime
> parameter: it doesn't do what I intuitively expect it to either.  It
> seems like if I set maxtime to x number of minutes, it submits jobs of
> at most x - 1 minutes duration.  
> 
> Is this the intended behaviour?  Is maxTime rounded down to the
> nearest minute?  Should I understand maxTime as meaning "only submit
> jobs that are strictly less than durations"?
> 
> - Tim
> 
> On Fri, Jun 3, 2011 at 10:15 AM, Michael Wilde <wilde at mcs.anl.gov>
> wrote:
>         Could you add a note on this to the trunk user guide?
>         
>         
>         Thanks,
>         
>         
>         Mike
>         
>         
>         
>         ______________________________________________________________
>         
>                 That did the trick. I bumped up the maxtime to 300 and
>                 it ran immediately. Thanks for the info!
>                 
>                 David
>                 
>                 On Fri, Jun 3, 2011 at 9:54 AM, Michael Wilde
>                 <wilde at mcs.anl.gov> wrote:
>                         David,
>                         
>                         
>                         Im not sure what coasters is thinking here.
>                          But first thing I would try is to set the
>                         maxtime value in sites.xml (which is in
>                         integer seconds) to something like 300 to make
>                         coasters realize that it can fit at least 10
>                         30-second app calls into the 300 second
>                         coaster block.
>                         
>                         
>                         With maxtime < maxwalltime coasters may be
>                         erroneously starting a block but finding that
>                         its unable to fit *any* app calls into it.
>                         
>                         
>                         There are also settings you can apply
>                         (overallocation etc) to make maxtime more of
>                         an "exact time" setting. For example, if you
>                         do this:
>                         
>                         
>                             <profile namespace="globus"
>                         key="maxTime">1800</profile>
>                             <profile namespace="globus"
>                         key="lowOverAllocation">100</profile>
>                             <profile namespace="globus"
>                         key="highOverAllocation">100</profile>
>                         
>                         
>                         ...then each coaster block started should have
>                         a maxwalltime of 1800 secs.
>                         
>                         
>                         But your app maxwalltime needs to fit into
>                         this block time.
>                         
>                         
>                         - Mike
>                         
>                         
>                         
>                         
>                         
>                         
>                         
>                         
>                         
>                         ______________________________________________
>                                 
>                                 Hello,
>                                 
>                                 I am trying to use the shared queue on
>                                 Fusion. This queue requires a walltime
>                                 of less than one hour. I have all of
>                                 the applications in my tc.data file
>                                 set up with a walltime of 30 seconds.
>                                 In my sites.xml, I specify a maxtime
>                                 of 10. However, when Swift generates
>                                 the PBS submit file, it specifies a
>                                 walltime of 00:00:00 which prevents it
>                                 from running.
>                                 
>                                 How can I make Swift set the walltime
>                                 in these PBS submit scripts?
>                                 
>                                 Thanks,
>                                 David
>                                 
>                                 
>                                 
>                                 _______________________________________________
>                                 Swift-devel mailing list
>                                 Swift-devel at ci.uchicago.edu
>                                 http://mail.ci.uchicago.edu/mailman/listinfo/swift-devel
>                         
>                         
>                         
>                         -- 
>                         Michael Wilde
>                         Computation Institute, University of Chicago
>                         Mathematics and Computer Science Division
>                         Argonne National Laboratory
>                         
>                         
>                 
>         
>         
>         
>         -- 
>         Michael Wilde
>         Computation Institute, University of Chicago
>         Mathematics and Computer Science Division
>         Argonne National Laboratory
>         
>         
>         
>         _______________________________________________
>         Swift-devel mailing list
>         Swift-devel at ci.uchicago.edu
>         http://mail.ci.uchicago.edu/mailman/listinfo/swift-devel
>         
> 
> _______________________________________________
> Swift-devel mailing list
> Swift-devel at ci.uchicago.edu
> http://mail.ci.uchicago.edu/mailman/listinfo/swift-devel