25.06.2015 Views

Administering Platform LSF - SAS

Administering Platform LSF - SAS

Administering Platform LSF - SAS

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

About Resource Allocation Limits<br />

About Resource Allocation Limits<br />

Contents ◆ “What resource allocation limits do” on page 258<br />

◆ “How <strong>LSF</strong> enforces limits” on page 259<br />

◆ “How <strong>LSF</strong> counts resources” on page 259<br />

◆ “Limits for resource consumers” on page 260<br />

What resource allocation limits do<br />

Jobs must specify<br />

resource<br />

requirements<br />

By default, resource consumers like users, hosts, queues, or projects are not<br />

limited in the resources available to them for running jobs. Resource<br />

allocation limits configured in lsb.resources restrict:<br />

◆ The maximum amount of a resource requested by a job that can be<br />

allocated during job scheduling for different classes of jobs to start<br />

◆ Which resource consumers the limits apply to<br />

If all of the resource has been consumed, no more jobs can be started until<br />

some of the resource is released.<br />

For example, by limiting maximum amount of memory for each of your hosts,<br />

you can make sure that your system operates at optimal performance. By<br />

defining a memory limit for some users submitting jobs to a particular queue<br />

and a specified set of hosts, you can prevent these users from using up all the<br />

memory in the system at one time.<br />

For limits to apply, the job must specify resource requirements (bsub -R<br />

rusage string or RES_REQ in lsb.queues). For example, the a memory<br />

allocation limit of 4 MB is configured in lsb.resources:<br />

Begin Limit<br />

NAME = mem_limit1<br />

MEM = 4<br />

End Limit<br />

A is job submitted with an rusage resource requirement that exceeds this limit:<br />

% bsub -R"rusage[mem=5]" uname<br />

and remains pending:<br />

% bjobs -p 600<br />

JOBID USER STAT QUEUE FROM_HOST EXEC_HOST JOB_NAME SUBMIT_TIME<br />

600 user1 PEND normal suplin02 uname Aug 12 14:05<br />

Resource (mem) limit defined cluster-wide has been reached;<br />

A job is submitted with a resource requirement within the configured limit:<br />

% bsub -R"rusage[mem=3]" sleep 100<br />

is allowed to run:<br />

% bjobs<br />

JOBID USER STAT QUEUE FROM_HOST EXEC_HOST JOB_NAME SUBMIT_TIME<br />

600 user1 PEND normal hostA uname Aug 12 14:05<br />

604 user1 RUN normal hostA sleep 100 Aug 12 14:09<br />

258<br />

<strong>Administering</strong> <strong>Platform</strong> <strong>LSF</strong>

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!