On 22 August 2012 23:53, Joseph Farran jfar...@uci.edu wrote:
Hi.
I have a GPU node with 24 Intel cores and 4 GPU Tesla cards.
My configuration has:
The node:
# qconf -se compute-1-14 | egrep gpu|processors
complex_valuesgpu=4
processors24
The complex setup:
qconf
On 22 August 2012 21:50, Henrichs, Juryk juryk.henri...@gl-group.comwrote:
Hi,
Reuti re...@staff.uni-marburg.de
Mittwoch, 22. August 2012 22:19
Hi,
Am 22.08.2012 um 21:39 schrieb Henrichs, Juryk:
we have a heterogeneous cluster consisting of nodes with 32 and 48
cpu's. Some of
Am 23.08.2012 um 09:32 schrieb William Hay:
snip
You have consumable set to YES which means the request is multiplied
by the number of slots you request 64 so you can't allocate them.
Assuming you have a recent version of Grid Engine you can set the
consumable setting to JOB. This will mean
Am 22.08.2012 um 22:50 schrieb Henrichs, Juryk:
Hi,
compose-unknown-contact.jpgReuti Mittwoch, 22. August 2012 22:19
Hi,
Am 22.08.2012 um 21:39 schrieb Henrichs, Juryk:
we have a heterogeneous cluster consisting of nodes with 32 and 48
cpu's. Some of our jobs are best run
What you could do is creating a queue for each GPU you
have on a host and assign them a queue exclusive GPU complex.
The amount of GPU queues are limiting then the amount of
GPU jobs. Then the total amount of cpu cores must be limited
differently by a RQS on a per host basis.
Daniel
Am
Am 22.08.2012 um 11:35 schrieb William Hay:
I'm looking to add support for BLCR into our grid engine
configuration. A quick google suggests the scripts here
https://github.com/HPCKP/BLCR-GridEngine-Integration should be useful
for such integration. Not wishing to engage in cargo cult
Am 22.08.2012 um 15:54 schrieb Dave Love:
Erik Soyez e.so...@science-computing.de writes:
Good day users,
does anybody know if this bug
http://www.mentby.com/Group/grid-engine/wildcarded-pe-name-circumvents-queue-sorting.html
has been fixed in any son of gridengine version?
I
Hi,
Am 22.08.2012 um 23:42 schrieb Henrichs, Juryk:
I tried the safety kill. Unfortunately that does not do the trick.
No idea what to make of it, but the job is restarted as expected as it spans
over not more than 15 nodes (or 120 slots) . If it spans more than that, it is
not restarted
The SGE site (arc.liv.ac.uk) is down until tomorrow morning (UK time),
should people be trying to access it. At least it _should_ be back
early morning.
--
Community Grid Engine: http://arc.liv.ac.uk/SGE/
___
users mailing list
users@gridengine.org
Wagner, Justin jwag...@ciena.com writes:
I see that SoGE has released version 8.1.1
Is there any documentation or recommendations as to how to upgrade a
machine/cluster already running 8.1.0?
It's the same as for any other upwards-compatible version, roughly as
described in the Oracle docs.
Reuti re...@staff.uni-marburg.de writes:
What needs documenting now? (I checked the lists of expanded variables
in the various instances against the code, but...)
nothing has to be changed. I posted your link as there it's corrected,
in contrast to the mentioned version 6.2u5 of the OP.
Thanks William.
Setting the consumable to JOB did the trick!
Best,
Joseph
On 08/23/2012 12:32 AM, William Hay wrote:
On 22 August 2012 23:53, Joseph Farranjfar...@uci.edu wrote:
You have consumable set to YES which means the request is multiplied
by the number of slots you request 64 so you
Hi Dave.
Any updates when the bug that causes sge_shepherd to run at 100% when one uses
qrsh is going to be fixed for sge 8.1.1?
I just tested it using qrsh and the bug is there.
Joseph
___
users mailing list
users@gridengine.org
Hi Dave.
Any updates when the bug that causes sge_shepherd to run at 100% when one uses
qrsh is going to be fixed for sge 8.1.1?
I just tested it using qrsh and the bug is there.
Joseph
___
users mailing list
users@gridengine.org
Howdy.
Is there a flag one can set on a job so that it will be killed instead of being
suspended for subordinate queue?
So if a job is running on a subordinate queue and the scheduler suspends it, to
have the job be killed instead?
Joseph
___
15 matches
Mail list logo
