No, SGE does not work that way.  The ‘sharetree’/Fairshare policy is a global 
policy that is applied across all jobs in the system, the same is true of the 
Functional policy it is applied globally and not ‘per queue’.  It is possible 
to setup the share tree to provide similar functionality (but it is beyond me, 
others on the list will have to help you configure that.).

Regards,

Bill.

> On Aug 15, 2016, at 5:24 PM, Mun Johl <[email protected]> wrote:
> 
> Hi all,
> 
> I just realized I forgot to mention one very importance criterion for our SGE 
> setup: Not only do we want equal priority per user, but we also want the 
> fairness policy to be per queue.  That is, if I launch one job on 
> first.q--which is otherwise unused; and then I launch 10 jobs on second.q 
> which already has jobs queued by three other people, the expectation is that 
> one out of four jobs dispatched from second.q will be mine--even though the 
> job on first.q is still running.
> 
> Is that how SGE will work with the Functional Policy?
> 
> Thanks,
> 
> --
> Mun
> 
> 
> 
> On Fri, Aug 12, 2016 at 10:51 PM, Mun Johl <[email protected] 
> <mailto:[email protected]>> wrote:
> Hi all,
> 
> I just thought I'd get a sanity check from you all before I actually make the 
> SGE changes.  As a reminder, we basically want to implement a fairness scheme 
> solely based on user.  So if User-A launches 10 jobs, and User-B launches 10 
> jobs--and let's say there is only one execution host--then we want User-A and 
> User-B's jobs to dispatched in a round-robin fashion.
> 
> Based on the information you folks have provided, it seems the Functional 
> Policy is the most appropriate for us.  The Share Tree Policy's historical 
> usage characteristic would probably not be appreciated by some folks I'm 
> afraid (unless the lifetime parameter could be set to something on the order 
> of minutes--which the documentation seems to state is not possible).
> 
> Regarding how to actually make this change: I was planning to use the Policy 
> Configuration tool in QMON and simply selecting the "Functional Policy" 
> button.  We don't have too many users at this point so I plan to add them 
> manually and then set the number of total functional tickets to be 200 per 
> user (e.g.).  And I will Clear the "Share Functional Ticket" button so that 
> each job has the same relative priority.
> 
> Am I close?  Anything I've missed or misunderstood?
> 
> Thanks,
> 
> --
> Mun
> 
> 
> On Thu, Aug 11, 2016 at 4:40 PM, Fotis Georgatos <[email protected] 
> <mailto:[email protected]>> wrote:
> And if you need a tool to keep an eye on the action as it happens, have a 
> look at qtop:
> 
> http://github.com/qtop/qtop <http://github.com/qtop/qtop>
> 
> Policy application monitoring at your fingertips.
> 
> Enjoy, F.
> 
> On Thursday, August 11, 2016, Mun Johl <[email protected] 
> <mailto:[email protected]>> wrote:
> Hi Sean, Christopher,
> 
> Thanks for the link, Sean.  I'll definitely give that a read and see if I can 
> figure out the details (I'm kind of new to configuring SGE).  And thanks to 
> both of you for your feedback.
> 
> Regards,
> 
> --
> Mun
> 
> 
> On Thu, Aug 11, 2016 at 5:03 AM, Sean Smith <[email protected] <>> 
> wrote:
> I will add that I just didn't provide a link we use this in production at 
> Soft Machines and it works well.....
> 
> Sean
> From: Christopher Heiny [[email protected] <>]
> Sent: Thursday, August 11, 2016 4:33 AM
> To: Sean Smith
> Cc: [email protected] <>; Mun Johl
> Subject: Re: [gridengine users] Is round-robin scheduling per user possible?
> 
> 
> On Aug 10, 2016 11:49 PM, "Sean Smith" <[email protected] <>> wrote:
> >
> > I would recommend reading this.
> >
> > http://arc.liv.ac.uk/SGE/howto/sge-configs.html#_fair_share 
> > <http://arc.liv.ac.uk/SGE/howto/sge-configs.html#_fair_share>
> Hi Mun,
> 
> We use the fair share approach that Sean links to provide round robin 
> scheduling within queues at our site.
> 
> Cheers,
> Chris
> 
> >
> > Sean
> > ________________________________
> > From: [email protected] <> [[email protected] <>] on 
> > behalf of Mun Johl [[email protected] <>]
> > Sent: Wednesday, August 10, 2016 8:27 PM
> > To: [email protected] <>
> > Subject: [gridengine users] Is round-robin scheduling per user possible?
> >
> > Hi,
> >
> > First a simple question: How do I change the priority of a queue?  I 
> > thought that would be trivial via qmon; but I couldn't find where the 
> > priority could be changed (at least, not in our setup).
> >
> > Now, my real question is this: Is it possible to configure SGE such that 
> > jobs are dispatched to execution hosts on a round-robin per user 
> > configuration?  For example, if User-A queues up 10 jobs, and then User-B 
> > queues up 10 jobs to the same queue; can SGE be configured to dispatch each 
> > of the 20 jobs to execution hosts in a round-robin fashion per user?  If 
> > so, how?
> >
> > If the above is not possible, then I'm thinking of creating a queue per 
> > user.  In that scenario, is it possible to configure SGE to dispatch to 
> > execution hosts in a round-robin fashion per queue?
> >
> > Many thanks,
> >
> > --
> > Mun
> >
> > _______________________________________________
> > users mailing list
> > [email protected] <>
> > https://gridengine.org/mailman/listinfo/users 
> > <https://gridengine.org/mailman/listinfo/users>
> >
> 
> 
> 
> 
> --
> echo "sysadmin know better bash than english"|sed s/min/mins/ \
>   | sed 's/better bash/bash better/' # signal detected in a CERN forum
> 
> 
> 
> 
> _______________________________________________
> users mailing list
> [email protected]
> https://gridengine.org/mailman/listinfo/users

William Bryce | VP Products
Univa Corporation, Toronto
E: [email protected] | D: 647-9742841 | Toll-Free (800) 370-5320
W: Univa.com <http://univa.com/> | FB: facebook.com/univa.corporation 
<http://facebook.com/univa.corporation> | T: twitter.com/Grid_Engine 
<http://twitter.com/Grid_Engine>

Attachment: signature.asc
Description: Message signed with OpenPGP using GPGMail

_______________________________________________
users mailing list
[email protected]
https://gridengine.org/mailman/listinfo/users

Reply via email to