[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.
John Hearns john.hearns at streamline-computing.comFri Apr 20 00:10:09 PDT 2007
- Previous message: [Beowulf] scheduler policy design
- Next message: [Beowulf] scheduler policy design
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Toon Knapen wrote:
> Additionally, in the case above, for optimising the efficiency of the
> node, I might prefer to launch just 1 process which uses 4 threads to
> perform multi-threaded (BLAS) calculations.
We help out customers deal with problems like that, and the above
example on serial jobs.
The answer to this one would be to create a parallel queue with just one
job slot, and prevent any other jobs from running on the node. The
parallel job then gets the full resources of the node, and can run the
multi-threaded calculations you want.
If you don't want jobs to be allocated that way, we have a 'multiway'
queue for running several jobs per host.
--
John Hearns
Senior HPC Engineer
Streamline Computing,
The Innovation Centre, Warwick Technology Park,
Gallows Hill, Warwick CV34 6UW
Office: 01926 623130 Mobile: 07841 231235
- 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
