25.06.2015 Views

Administering Platform LSF - SAS

Administering Platform LSF - SAS

Administering Platform LSF - SAS

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

CPU Time and Run Time Normalization<br />

Normalization host<br />

Chapter 26<br />

Runtime Resource Usage Limits<br />

To set the CPU time limit and run time limit for jobs in a platform-independent<br />

way, <strong>LSF</strong> scales the limits by the CPU factor of the hosts involved. When a job<br />

is dispatched to a host for execution, the limits are then normalized according<br />

to the CPU factor of the execution host.<br />

Whenever a normalized CPU time or run time is given, the actual time on the<br />

execution host is the specified time multiplied by the CPU factor of the<br />

normalization host then divided by the CPU factor of the execution host.<br />

If ABS_RUNLIMIT=Y is defined in lsb.params, the run time limit is not<br />

normalized by the host CPU factor. Absolute wall-clock run time is used for all<br />

jobs submitted with a run limit.<br />

If no host or host model is given with the CPU time or run time, <strong>LSF</strong> uses the<br />

default CPU time normalization host defined at the queue level<br />

(DEFAULT_HOST_SPEC in lsb.queues) if it has been configured, otherwise<br />

uses the default CPU time normalization host defined at the cluster level<br />

(DEFAULT_HOST_SPEC in lsb.params) if it has been configured, otherwise<br />

uses the submission host.<br />

Example<br />

CPULIMIT=10/hostA<br />

If hostA has a CPU factor of 2, and hostB has a CPU factor of 1 (hostB is<br />

slower than hostA), this specifies an actual time limit of 10 minutes on hostA,<br />

or on any other host that has a CPU factor of 2. However, if hostB is the<br />

execution host, the actual time limit on hostB is 20 minutes (10 * 2 / 1).<br />

Normalization hosts for default CPU and run time limits<br />

The first valid CPU factor encountered is used for both CPU limit and run time<br />

limit. To be valid, a host specification must be a valid host name that is a<br />

member of the <strong>LSF</strong> cluster. The CPU factor is used even if the specified limit is<br />

not valid.<br />

If the CPU and run limit have different host specifications, the CPU limit host<br />

specification is enforced.<br />

If no host or host model is given with the CPU or run time limits, <strong>LSF</strong><br />

determines the default normalization host according to the following priority:<br />

1 DEFAULT_HOST_SPEC is configured in lsb.queues<br />

2 DEFAULT_HOST_SPEC is configured in lsb.params<br />

3 If DEFAULT_HOST_SPEC is not configured in lsb.queues or<br />

lsb.params, host with the largest CPU factor is used.<br />

CPU time display (bacct, bhist, bqueues)<br />

Normalized CPU time is displayed in the output of bqueues. CPU time is not<br />

normalized in the output if bacct and bhist.<br />

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

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

Saved successfully!

Ooh no, something went wrong!