You can run jobs at different sizes and durations on Delta CPU. The following lists the different queues that you can submit to, describing how many nodes you get, how long you can run, the type of resources you get, and the average wait time.
Delta uses the Slurm scheduler. If you do not request a wall-clock time or memory amount, Delta defaults to 30 minutes and 1,000 MB of memory per core. Submit batch jobs with sbatch; use srun to run a command or start an interactive job; and use salloc to reserve resources for multiple commands. For instructions and Delta-specific examples, see [Delta Batch Jobs] for sbatch and [Delta Interactive Jobs] for srun and salloc.
Compute resources are also available through [Delta Open OnDemand] applications such as JupyterLab, VS Code Code Server, and noVNC Desktop.
Track your work with the usual Slurm commands: squeue -u $USER shows the status of your queued and running jobs, scontrol show job followed by a job ID shows the detail for one job, sinfo -a summarizes all Delta partitions and their node states, and scancel followed by a job ID cancels a queued job or terminates a running one.
Delta CPU jobs should use cpu for standard production jobs, cpu-preempt for checkpointing-capable jobs that can tolerate interruption, and cpu-interactive for short interactive sessions.
Wall-time limits and node counts for each partition are in the table below.
Node sharing is the default. To request exclusive use of a CPU node, request all consumable resources for the node or use --exclusive --mem=0. CPU and GPU allocations use separate local charge accounts, so submit CPU jobs with the appropriate Delta CPU account.
For complete job guidance, see [Delta Running Jobs]. Example scripts for serial, MPI, OpenMP, hybrid, and other job types are available in [Delta Sample Scripts].