As you say, you modify priority in GridEngine rather than order as such. We use (or are looking at using) a couple of methods to manage the kind of ordering you're talking about:
1) POSIX Priority - We have 5 levels: Highest, High, Normal, Low, Whenever which just map to 600,300,0,-300,-600 and then weight Priority much higher than tickets. If we have a super important job and they're screaming it must run, I just bump the priority number to 1000. 2) Share tree/Functional. We're looking to deploy a setup that looks like: Project A - 80 Project B - 20 Company Priority - 1000000 When it's decided that something's a company priority, it's obviously going to get pretty much all the tickest. I guess you could just use POSIX priorities and turn weight all the urgency/ticket stuff to 0. Anything not set with a higher/lower priority would just run FIFO (I haven't tried this and I might be wrong) Stephen On Wed, Oct 5, 2011 at 7:42 PM, Rick Reynolds II <[email protected]> wrote: > We're looking at using SGE to replace a home-grown queuing system that is > showing its age in terms of legacy maintenance, etc. > > The previous system was strictly FIFO for each queue. You add a job to a > specific queue, and it waits its turn. As I'm reading more about SGE and the > various policies that can be used to control queuing, I'm getting the > impression that real, hard control of the order of jobs isn't something that > SGE provides when you're using the different policies to help it determine > job priorities. Is that right? > > We're interested in being able to classify certain jobs as higher priority. > And I'd guess we'd specify policies to guide the ticket allocation for those > kinds of jobs. But if I'm using those policies will I still be able to > specify something like "give this specific job the next position in the > queue"? > > Thanks, > Rick Reynolds > -- > "He who breaks a thing to find out what it is, has left the path of wisdom." > -- Gandalf > > > > > > This e-mail message is intended for the recipient only and contains > information which is CONFIDENTIAL and which may be proprietary to ECI > Telecom. If you have received this transmission in error, please inform us by > e-mail, phone or fax, and then delete the original and all copies thereof. > > > _______________________________________________ > users mailing list > [email protected] > https://gridengine.org/mailman/listinfo/users > -- Stephen http://lensframephoto.com _______________________________________________ users mailing list [email protected] https://gridengine.org/mailman/listinfo/users
