[GE users] when a queue is full
peirans at cs.uoregon.edu
Thu Dec 8 00:29:28 GMT 2005
[ The following text is in the "ISO-8859-1" character set. ]
[ Your display is set for the "ISO-8859-10" character set. ]
[ Some special characters may be displayed incorrectly. ]
We have an Apple cluster running Grid Engine. We observed much longer
execution time of two subjobs scheduled to the same duel-CPU node,
comparing to directly send the two sub-jobs about simultaneously by dsh
to the same node. The time difference is two minutes versus 15 seconds.
When I tried qstat -j during the executions, for the first case, I got
the queue is full info as below, but not for the second case.
usage 2: cpu=00:00:00, mem=0.00000 GBs, io=0.00000,
usage 3: cpu=00:00:00, mem=0.00000 GBs, io=0.00000,
scheduling info: queue instance
"all.q at node005.cluster.private" dropped because it is full
I am wondering at what circumstance a queue would be deemed full (no
spare CPU, no spare memory?). Is that truly full or is that an
estimate? Seems that when it is deemed full, it took much longer for
the job to be done. Could the configuration parameters be tweaked
somehow to limit/avoid this happening? Here is our current configuration:
job_load_adjustments NONE --- should we adjust?
Any comments and ideas would be very much appreciated!
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