at basic level fairshare fit your need there is also fix ticket like functional by dept and ergency ticket that admin can override other jobs regards
Sent from my iPad On May 29, 2012, at 3:50, Jake Carroll <[email protected]> wrote: > Hi all. > > Haven't posted much here yet, as I'm new to the list/learning. > > Irrespective, I have a question of the community. > > One of the things I've always liked the idea of is to be able to dynamically > allocate "slots" or a number of jobs that can run for a single user based > upon the global load of the cluster/nodes. Such that, it gives an overall > very efficient utilisation of a cluster. > > An example might be a cluster sitting idle. Let's say that it's got 1024 > "slots" doing nothing and a user jumps on. Some convention wisdom/queue > semantics we use is a parameter that says the user cannot "take" more than > 400 or 500 slots a a time. > > That's great, but it leaves the rest of the cluster sitting cold. > > What I'd really like to be able to do is dynamically load balance load such > that if the cluster is idle, a user can take up a great significant portion > of it. If a cluster is fairly heavily subscribed, a user gets less of a slice > as they log in, but a "fairshare" policy means they get the next-best swing > at it if another user takes up a great deal of slots for a great time period. > > I am aware that schedulers such as PBS Pro have some form of > technique/complexes for addressing things like this. > > I appreciate it's fairly abstract, but just wondering if SGE/OGE have any > similar semantics? > > Thank you for your time, all. > > --JC > _______________________________________________ > users mailing list > [email protected] > https://gridengine.org/mailman/listinfo/users _______________________________________________ users mailing list [email protected] https://gridengine.org/mailman/listinfo/users
