Hi, Am 23.10.2012 um 21:41 schrieb Lars van der bijl:
> I've got 2 queue's > > $ qconf -sq final.q > qname final.q > hostlist @allhosts > suspend_thresholds NONE > nsuspend 1 > suspend_interval 00:01:00 > pe_list make smp > rerun TRUE > > > $ qconf -sq quick.q > qname quick.q > hostlist @allhosts > suspend_thresholds NONE > nsuspend 1 > suspend_interval 00:01:00 > pe_list make smp > rerun TRUE > subordinate_list final.q=1 > > we have about 325 procs and both queue's have access to the same machines. > > what I'd except to see is if I have 200 slots running in final.q and I > submit a task to quick.q that it would suspend the task in final.q and > push the new task in front. > however what I am seeing that that only 32 slots are being used. and > not all tasks are being pushed in front of the final.q > > we only use parallel submission in case that makes a difference. > > what could I change to get this behavior? hard to tell from the information you posted, as I don't know how 32 are in any way related to 325 procs without knowing more details. So some remarks, maybe you can refine the setup or question then: - the subordinate_list will only work "per exechost" queue instance - in your current setup all slots from queue instance on a particular exechost will be suspended as soon as one slot in quick.q is used - (may you are looking for a slot-wise subordination?) - jobs in the quick.q don't have a higher priority - it's best not to submit to queues in SGE, but think of "request resources" and SGE will select an appropriate queue for your job For your setup this could mean to define a BOOL complex "quick" as "requestable FORCED" and attach it to the quick.q, then request "-l quick" (which implies "-l quick=TRUE") and in addition attach a high "urgency" value to this complex. Then they should go also to the top of the list. And only "quick" will run in this queue. -- Reuti _______________________________________________ users mailing list [email protected] https://gridengine.org/mailman/listinfo/users
