[Beowulf] scheduler policy design
Many of your questions may have already been answered in earlier discussions or in the FAQ. The search results page will indicate current discussions as well as past list serves, articles, and papers.
Leif Nixon nixon at nsc.liu.seThu Apr 26 03:29:03 PDT 2007
- Previous message: [Beowulf] scheduler policy design
- Next message: [Beowulf] scheduler policy design
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Bogdan Costescu <Bogdan.Costescu at iwr.uni-heidelberg.de> writes: > For example, if the queue is limited to 24h maximum runtime and they > would set 24h as their requirement, thinking that it would certainly > cover what they want and the job would not run anyway longer than > that, as it would be killed by the scheduler. We do advance reservation with backfill, so short jobs will on average start sooner than long jobs. We find that this is sufficient motivation for the users to at least try to set reasonable walltime values. -- Leif Nixon - Systems expert ------------------------------------------------------------ National Supercomputer Centre - Linkoping University ------------------------------------------------------------
- Previous message: [Beowulf] scheduler policy design
- Next message: [Beowulf] scheduler policy design
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Beowulf mailing list
