Am 16.01.2014 um 00:24 schrieb Joseph Farran:
Allison,
I love Grid Engine but this is the one feature I truly miss from Torque:
-l nodes=x:ppn=[count]
RFE could be the setting allocation_rule $user_defined in a PE, which would
still be necessary to be requested during job submission.
Am 16.01.2014 um 05:24 schrieb tele...@shaw.ca:
Sorry - you're correct, I meant -l nodes=1:ppn=[count] . :-)
Hmmm...we've had some requests from clients specifically to support SGE, but
this is a pretty key part of our functionality. Currently we can submit, but
without the way to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 15/01/14 22:28, Allison Walters wrote:
We have OpenMP jobs that need a user-defined (usually more than one
but less than all) number of cores on a single node for each job.
In addition to running these jobs, our program has an interface to
the
Am 16.01.2014 um 09:54 schrieb Reuti:
Am 16.01.2014 um 05:24 schrieb tele...@shaw.ca:
Sorry - you're correct, I meant -l nodes=1:ppn=[count] . :-)
Hmmm...we've had some requests from clients specifically to support SGE, but
this is a pretty key part of our functionality. Currently we
- Original Message -
From: Reuti re...@staff.uni-marburg.de
The hardware doesn't matter much for such a PE, more the various defined
queues: to which one you will attach the newly created PE?
During installation you can check whether there is such a PE (scan all PEs
and look for
Great info - thank you!
-Allison
- Original Message -
From: William Hay w@ucl.ac.uk
To: Allison Walters tele...@shaw.ca, users@gridengine.org
Sent: Thursday, January 16, 2014 2:22:04 AM
Subject: Re: [gridengine users] Requesting multiple cores on one node
I think the difference
Am 15.01.2014 um 23:28 schrieb Allison Walters:
We have OpenMP jobs that need a user-defined (usually more than one but less
than all) number of cores on a single node for each job. In addition to
running these jobs, our program has an interface to the cluster so they can
submit jobs
Allison,
I love Grid Engine but this is the one feature I truly miss from Torque:
-l nodes=x:ppn=[count]
Reuti,
We have a complex setup trying to accomplish this same thing and it kind of
works but we have an issue with job not starting when jobs are running on a
subordinate queue.
First,
Sorry - you're correct, I meant -l nodes=1:ppn=[count] . :-)
Hmmm...we've had some requests from clients specifically to support SGE,
but this is a pretty key part of our functionality. Currently we can
submit, but without the way to specify cores, the clients won't get the
timing results
