[GE users] Job priority

Brian Pontz bpontz at ll.mit.edu
Wed May 23 19:40:59 BST 2007

I'm in testing stages at this point. Basically I wrote a test script
that has a loop and qsub's 500 of the same jobs.

for i in `seq 1 500`; do
        PRIO=`perl -e 'srand; $foo=int(rand(1024)); print $foo'`
	qsub -p $PRIO -cwd  -o /dev/null -e /dev/null /home/user/test.sh


test.sh is basically a shell script that sleeps for random amounts of
time between 10 and 300 seconds. The amount of slots available is about


On Wed, 2007-05-23 at 14:12 -0400, John Coldrick wrote:
> On Wednesday 23 May 2007 13:54, Brian Pontz wrote:
> > SGE version is 6.0u8
> >
> > Jobs are submitted via
> >
> > qsub -p 20 -cwd  -o /dev/null -e /dev/null /home/user/test.sh
> 	It's probably useful for you to quickly step through the actual process you 
> went through, step by step.  Once a job starts running, the "running order" 
> is meaningless, so unless you're going through very specific steps of holding 
> back jobs from running and then letting them go at once, I'm not clear how 
> you could tell about run order, unless your outnumbering your available 
> slots.
> 	Note there's a slight delay while SGE evaluates the priority(it's based on 
> potentially numerous things, but by default, mostly the priority).  You'll 
> see it's priority "0" while it does that, then it will kick in with ".57941" 
> or some other float between 0 and 1.
> 	Prioritizing does work, so it's just a matter of figuring out your process.
> 	Cheers,
> 	J.C.

To unsubscribe, e-mail: users-unsubscribe at gridengine.sunsource.net
For additional commands, e-mail: users-help at gridengine.sunsource.net

More information about the gridengine-users mailing list