Sorry for the late delay - I've been on holiday and only now starting to catch up. To add to Donal's fine response. If you do come up with a good set of custom extensions for some resource managers please let us know and we can see about making them into normative extensions. steve.. Donal K. Fellows wrote:
Peter G. Lane wrote:
Just to make sure I'm understanding your point completely, neither JSDL nor any of it's normative extensions provide a way, not including custom extensions, to specify resource limits for jobs submitted to resource managers (i.e. PBS, LSF, Condor, ...). The POSIXApplication limits should be used only by applications that are able to directly set the ulimit values before executing a process. Is this is a valid statement?
To be exact, we expect people to specify (in the jsdl:Resources section) what resources their job needs to execute successfully (if they specify too little, that's too bad) and for the resource manager to use that information to compute how many resources to allocate to the job. It is also up to the resource manager to choose how to implement said allocation; JSDL does not mandate any particular mechanism. If the mechanism chosen includes the use of POSIX limits, it is obviously incumbent upon the implementation to set the limits such that the requirements within the POSIXApplication section are also met; I would not expect any implementation to allow the Limits to be used to gain any extra allocation of resources above and beyond what was asked for in the Resources section.
One way of doing this might be for the resource manager to first set up hard limits and then to use the various PA/*Limits to refine those with extra soft limits.
Donal.