LSF Version 7.3 - Using Platform LSF HPC

RESOURCENAME TYPE INTERVAL INCREASING DESCRIPTION
...
adapter_windows Numeric 30 N (free adapter windows on css0 on IBM SP)
ntbl_windows Numeric 30 N (free ntbl windows on IBM HPS)
poe Numeric 30 N (poe availability)
css0 Numeric 30 N (free adapter windows on css0 on IBM SP)
csss Numeric 30 N (free adapter windows on csss on IBM SP)
dedicated_tasks Numeric () Y (running dedicated tasks)
ip_tasks Numeric () Y (running IP tasks)
us_tasks Numeric () Y (running US tasks)
...
End Resource
You must edit lsf.cluster. cluster_name and allocate the external resources.
For example, to configure a switch adapter for six SP2 nodes (
sp2n1, sp2n1, sp2n3,
...,
sp2n6):
Begin ResourceMap
RESOURCENAME LOCATION
...
adapter_windows [default]
ntbl_windows [default]
css0 [default]
csss [default]
dedicated_tasks (0@[default])
ip_tasks (0@[default])
us_tasks (0@[default])
...
End ResourceMap
The adapter_windows and ntbl_windows resources are required for all POE jobs.
The other three resources are only required when you run IP and US jobs at the same
time.
To improve performance and scalability for large POE jobs, tune the following
lsf.conf parameters. The user's environment can override these.
◆ LSF_HPC_PJL_LOADENV_TIMEOUT
Timeout value in seconds for PJL to load or unload the environment. For example,
the time needed for IBM POE to load or unload adapter windows.
At job startup, the PJL times out if the first task fails to register within the specified
timeout value. At job shutdown, the PJL times out if it fails to exit after the last
Taskstarter termination report within the specified timeout value.
Default: LSF_HPC_PJL_LOADENV_TIMEOUT=300
◆ LSF_PAM_RUSAGE_UPD_FACTOR
This factor adjusts the update interval according to the following calculation:
RUSAGE_UPDATE_INTERVAL + num_tasks * 1 *
LSF_PAM_RUSAGE_UPD_FACTOR.