*Borax's 2 login nodes are: borax[2,5]

 

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.MACHINENAME

Web version of Borax Job Limits

Borax 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 Borax node contains dual-socket Intel Broadwell processors (2.1 GHz) each with 18 cores for a total of 36 cores/node and 128 GiB memory/node.

Scheduling

Batch jobs are scheduled through SLURM.

  • Interactive login: borax[2,5]
  • Pdebug:    borax[6-8]
  • Batch use:   borax[9-48]

 Maximum memory size and duration of jobs on Borax

    ---------------------------------------------------------------
                           INTERACTIVE             BATCH
                         MEMORY    CPU         MEMORY   CPU
    borax[2,5]          128 GiB     30 min     - Interactive Only -
    borax[6-8] (pdebug) 128 GiB     30 min     - Interactive Only -
    borax{9-48](pbatch) - Batch Only -         128 GiB    200 hrs
    ---------------------------------------------------------------

 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.

 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:

 SBATCH SCRIPT: #SBATCH -n number_of_cores

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

 Scratch Disk Space: Consult CZ File Systems Web Page

Documentation

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

 
Zone
CZ
Vendor
Penguin
User-Available Nodes
Login Nodes*
2
Batch Nodes
41
Debug Nodes
2
Total Nodes
48
CPUs
CPU Architecture
Intel Xeon E5-2695 v4
Cores/Node
36
Total Cores
1,728
Memory Total (GiB)
6,144
CPU Memory/Node (GiB)
128
Peak Performance
Peak PFLOPS (CPUs)
0.058
Peak PFLOPS (CPUs+GPUs)
0.058
Clock Speed (GHz)
2.1
Peak single CPU memory bandwidth ((GiB)/s)
77
OS
TOSS 4
Interconnect
N/A
Scheduling Policy (main batch queue)
core-scheduled
Scheduler
Slurm
Recommended location for parallel file space
/p/lustre[1,2]
Program
ASC
Class
CTS-1
Year Commissioned
2016
Compilers

Compilers (TOSS 3)
Documentation

Introduction to LC Resources

Linux Clusters Overview