users] Requirement to run longer jobs
Hi Chris,
Chris Samuel writes:
> On 3/7/19 8:49 am, David Baker wrote:
>
>> Does the above make sense or is it too complicated?
>
> [looks at our 14 partitions and 112 QOS's]
>
> Nope, that seems pretty simple. We do much the sam
Hi Chris,
Chris Samuel writes:
> On 3/7/19 8:49 am, David Baker wrote:
>
>> Does the above make sense or is it too complicated?
>
> [looks at our 14 partitions and 112 QOS's]
>
> Nope, that seems pretty simple. We do much the same here.
Out of interest, how many partitions and QOSs would an av
On 3/7/19 8:49 am, David Baker wrote:
Does the above make sense or is it too complicated?
[looks at our 14 partitions and 112 QOS's]
Nope, that seems pretty simple. We do much the same here.
All the best,
Chris
--
Chris Samuel : http://www.csamuel.org/ : Berkeley, CA, USA
The dual QoSes (or dual partition solution suggested by someone else)
should both work in allow select users to submit jobs with longer run
times. We use something like that on our cluster (though I confess it was
our first Slurm cluster and we might have overdid it with QoSes causing
scheduler to
Hi,
On Wed, Jul 03, 2019 at 03:49:44PM +, David Baker wrote:
> Hello,
>
>
> A few of our users have asked about running longer jobs on our cluster.
> Currently our main/default compute partition has a time limit of 2.5 days.
> Potentially, a handful of users need jobs to run up to 5 hours. R
Hello,
A few of our users have asked about running longer jobs on our cluster.
Currently our main/default compute partition has a time limit of 2.5 days.
Potentially, a handful of users need jobs to run up to 5 hours. Rather than
allow all users/jobs to have a run time limit of 5 days I wonder
