Job Limits

Each LC platform is a shared resource. Users are expected to adhere to the following usage policies to ensure that the resources can be effectively and productively used by everyone. You can view the policies on a system itself by running:

news job.lim.poodle

Web version of Poodle Job Limits

Poodle is an M&IC resource to be used for serial and on-node parallelism only. Jobs are scheduled per core. This system does not have a high-speed interconnect.

Hardware

Each Poodle batch node contains dual-socket Intel Xeon Platinum 8479 processors (2.0 GHz) each with 56 cores for a total of 112 cores/node and 256 GiB DDR5 memory/node.

UPDATE 8/2023: Poodle also has High Bandwidth Memory (HBM) nodes which contain dual-socket Intel(R) Xeon(R) CPU Max 9480 processors (1.9 GHz) each with 56 cores for a total of 112 cores/node and 128 GiB HBM memory/node.

Scheduling

Batch jobs are scheduled through SLURM.

•     Interactive login: poodle[17,18]
•     Pdebug: poodle[1-3]
•     Batch use: poodle[4-16,22-37]
•     HBM use: poodle[38-41]

    MAXIMUM MEMORY SIZE AND DURATION OF JOBS ON POODLE
    ---------------------------------------------------------------
                               INTERACTIVE       BATCH
                               MEMORY   CPU      MEMORY   CPU
    poodle[17,18]              256 GiB  30 min   - Interactive Only -
    poodle[1-3] (pdebug)       256 GiB  30 min   - Interactive Only -
    poodle[4-16,22-37](pbatch) - Batch Only -    256 GiB  200 hr
    poodle[38-41](phighmem)    - Batch Only -    128 GiB  200 hr
    ---------------------------------------------------------------

Pdebug is intended for debugging, visualization, and other inherently interactive work.  It is NOT intended for production work. Do not use pdebug to run batch jobs.  Do not chain jobs to run one after the other. Individuals who misuse the pdebug queue in this or any similar manner will be denied access to running jobs in the pdebug queue.

Interactive access to a batch node is allowed only while you have a batch job running on that node, and only for the purpose of monitoring your job. When logging into a batch node, be mindful of the impact your work has on the other jobs running on the node.

Jobs are limited to a single node.  Multiple users can run on the same node.  If the number of cores is not specified, the job is allocated to one core.  Use the following syntax in your batch script to specify the actual number of cores needed:

    MSUB SCRIPT:    #MSUB -l ttc=number_of_cores

    SBATCH SCRIPT:  #SBATCH  -n  number_of_cores

ALWAYS use the msub -l ttc or sbatch -n option when your job will use more than one task.

Scratch Disk Space: Consult CZ File Systems Web Page: https://lc.llnl.gov/fsstatus/fsstatus.cgi

Documentation

• Linux Clusters Tutorial Part One | Linux Clusters Part Two
• Slurm Tutorial (formerly Slurm and Moab)

Contact

Please call or send email to the LC Hotline if you have questions. LC Hotline | phone: 925-422-4531 | email: lc-hotline@llnl.gov