Archives


- Beowulf
- Beowulf Announce
- Scyld-users
- Beowulf on Debian

[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.

Search

Toon Knapen toon.knapen at fft.be
Thu Apr 26 02:06:50 PDT 2007


Tim Cutts wrote:
> 
> The compromise we ended up with is this set of LSF queues on our system 
> (a cluster with about 1500 job slots):
> 
> QUEUE_NAME      PRIO STATUS          MAX JL/U JL/P JL/H NJOBS  PEND   
> RUN  SUSP
> yesterday       500  Open:Active     200   10    -    -     1     0     
> 1     0
> normal           30  Open:Active       -    -    -    -   281   110   
> 171     0
> hugemem          30  Open:Active       -    -    -    -     3     0     
> 3     0
> long              3  Open:Active       -    -    -    -  4022  2987  
> 1035     0
> basement          1  Open:Active     300  200    -    -   127     0   
> 127     0
> 
> yesterday:
> 
> a special purpose high priority queue for the "I need it yesterday" 
> crowd.  No run length limits, but very limited in terms of how many 
> slots the user can use.
> 


Do you have slot reserved exclusively for the 'yesterday' queue or to 
any of the other queue's ?



More information about the Beowulf mailing list