[gridengine users] mem_free being treated as "per core" on certain queues
Joe Whitney
jwhitney at gmail.com
Wed Feb 29 22:14:01 UTC 2012
Hello,
I am having a simple problem where the behaviour of mem_free resource
requests are being treated differently on two different queues (actually,
separate installations of SGE).
For context, the hosts servicing queue.A have 32G/4cores available, while
those servicing queue.B have 24G/4cores available. All queues/nodes are
idle/empty when I perform the following tests.
On queue.A, the following jobs get scheduled and run as expected:
$ echo ls | qsub -q queue.A -pe smp 1 mem_free=20G #runs right away
$ echo ls | qsub -q queue.A -pe smp 2 mem_free=20G #also runs right away
On queue.B, only the first gets run:
$ echo ls | qsub -q queue.A -pe smp 1 mem_free=20G #runs right away
$ echo ls | qsub -q queue.A -pe smp 2 mem_free=20G #sits in 'qw' state
forever
Conjecture: mem_free is being treated as a "per-core" request for queue.B
but not for queue.A.
Question 1: is this possible?
Question 2: how do I fix queue.B so that it performs like queue.A?
Apologies if my terminology is not 100% correct; I deal with SGE
administration infrequently.
Thanks in advance for any suggestions,
Joe
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://gridengine.org/pipermail/users/attachments/20120229/b2428bea/attachment.html>
More information about the users
mailing list