LSF Version 7.3 - Using Platform LSF HPC

You can use CELL_LIST with the PSET[PTILE=cpus_per_cell] option. The PTILE
option allows the job pset to spread across several cells. The number of required cells
equals the number of requested processors divided by the PTILE value. The resulting
number of cells must be less than or equal to the number of cells in the cell list;
otherwise, the job remains pending.
For example, the following is a correct specification:
bsub -n 8 -ext "PSET[PTILE=2;CELL_LIST=1-4]" myjob
The job requests 8 CPUs spread over 4 cells (8/2=4), which is equal to the 4 cells
requested in the CELL_LIST option.
Viewing pset allocations for jobs
After a pset job starts to run, use bjobs -l to display the job pset ID. For example, if
LSF creates pset 23 on
hostA for job 329, bjobs shows:
bjobs -l 329
Job <329>, User <user1>, Project <default>, Status <RUN>, Queue <normal>, Ext
sched <PSET[]>, Command <sleep 60>
Thu Jan 22 12:04:31: Submitted from host <hostA>, CWD <$HOME>, 2 Processors
Requested;
Thu Jan 22 12:04:38: Started on 2 Hosts/Processors <2*hostA>, Execution Home
</home/user1>, Execution CWD </home/user1>;
Thu Jan 22 12:04:38: psetid=hostA:23;
Thu Jan 22 12:04:39: Resource usage collected.
MEM: 1 Mbytes; SWAP: 2 Mbytes; NTHREAD: 1
PGID: 18440; PIDs: 18440
SCHEDULING PARAMETERS:
r15s r1m r15m ut pg io ls it tmp swp mem
loadSched - - - - - - - - - - -
loadStop - - - - - - - - - - -
EXTERNAL MESSAGES:
MSG_ID FROM POST_TIME MESSAGE ATTACHMENT
0 - - - -
1 user1 Jan 22 12:04 PSET[]
Use bhist to display historical information about pset jobs:
bhist -l 329
Job <329>, User <user1>, Project <default>, Extsched <PSET[]>, Command <sleep
60>
Thu Jan 22 12:04:31: Submitted from host <hostA>, to Queue <normal>, CWD <$H
OME>, 2 Processors Requested;
Thu Jan 22 12:04:38: Dispatched to 2 Hosts/Processors <2*hostA>;
Thu Jan 22 12:04:38: psetid=hostA:23;
Thu Jan 22 12:04:39: Starting (Pid 18440);