Loading...

moabusers@supercluster.org

[Prev] Thread [Next]  |  [Prev] Date [Next]

Re: [Moabusers] specifying user job proc in standing reservations Sikora, Josef S Fri Oct 29 11:00:36 2010

I checked the documentation and you probably can't do what you want without a 
class. My only suggestion is to tie that class to the reservation so that you 
do not have to specify the nodes in two places:

SRCFG[name] CLASSLIST=&class_name

The & forces the class to utilize the reservation resources.

Josef


-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Richard Christie
Sent: Thursday, October 28, 2010 9:37 AM
To: Sikora, Josef S
Cc: [EMAIL PROTECTED]
Subject: Re: [Moabusers] specifying user job proc in standing reservations


Thanks for the suggestion, but I don't think PROCLIMIT will do
what I need.

If I define a reservation using a HOSTLIST that has a total of 100 cores,
I want to limit any one user from using more than, say, 30 cores at any
one time. I want users to be able to run on 30 cores in a single job, or
30 cores in 30 different jobs, but not more than 30 cores concurrently.

It looks to me like PROCLIMIT could only be used to prevent users from 
running a single job that asks for, say 30 cores; with this in place 
however, one user could still use up all 100 cores in the reservation.

thanks,
Richard


On Thu, 28 Oct 2010, Sikora, Josef S wrote:

> Try the PROCLIMIT parameter.  It is documented in section 7.1.5.2 of the Moab 
> Admin Guide, version 5.3.
>
> Josef
>
>
> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Richard 
> Christie
> Sent: Tuesday, October 26, 2010 8:02 PM
> To: [EMAIL PROTECTED]
> Subject: [Moabusers] specifying user job proc in standing reservations
>
> Hello,
>
> Is there anyway of limiting the number of CPU cores that a user can
> utilise in a standing reservation? Ideally, I'd like to specify something
> like:
>
> SRCFG[share] HOSTLIST=n1,n2,n3 MAXPROCPERUSER=4
>
> or better yet
>
> SRCFG[share] HOSTLIST=n1,n2,n3 MAXPROC[USER:sarah]=4
>
> but this doesn't seem to be possible from the Moab documentation.
>
> Do I have to create a class that uses this HOSTLIST to impose a user-based
> CPU core limit?
>
> thanks,
> Richard Christie
>
>
> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>  Richard A. Christie
>  Research Associate Professor
>  313 Eberly Hall                e-mail: [EMAIL PROTECTED]
>  University of Pittsburgh       url:    http://pro3.chem.pitt.edu/richard
>  Pittsburgh, PA 15260           tel:    412-624-8621
> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>
> _______________________________________________
> moabusers mailing list
> [EMAIL PROTECTED]
> http://www.supercluster.org/mailman/listinfo/moabusers
> _______________________________________________
> moabusers mailing list
> [EMAIL PROTECTED]
> http://www.supercluster.org/mailman/listinfo/moabusers
>
_______________________________________________
moabusers mailing list
[EMAIL PROTECTED]
http://www.supercluster.org/mailman/listinfo/moabusers
_______________________________________________
moabusers mailing list
[EMAIL PROTECTED]
http://www.supercluster.org/mailman/listinfo/moabusers