[Swift-user] Set maxtime > maxwalltime or your script will hang
Michael Wilde
wilde at mcs.anl.gov
Tue Apr 27 12:16:48 CDT 2010
On Apr 27, 2010, at 11:48 AM, Mihael Hategan wrote:
> A comment there:
> Set the "maxtime" coaster parameter if you know that the queue you are
> using has a limit to the time a job can have. Don't set it because your
> jobs have a certain maxwalltime. It's purpose is to prevent the creation
> of blocks that cannot be run on a given queue.
Mihael, can you clarify this (and the related text from the User Guide)?
Users almost always want to get their jobs into a "good" queue, and hence
they usually feel compelled to set maxtime. So more questions arise when
you try to figure out how to do this:
- How does coasters fill blocks?
- What LRM wall time will be used when maxtime is not specified?
(i.e, how many jobs will coasters place in a block)?
- Is coasters committing more jobs to specific blocks (and hence specific sites)
than the block has cores, when it computes its schedules?
Or just estimating what it may need?
More information about the Swift-user
mailing list