Skip to content

Commit b8251be

Browse files
committed
dump tutorial slides, format later
1 parent a5d6fa8 commit b8251be

1 file changed

Lines changed: 18 additions & 18 deletions

File tree

docs/hpc/05_submitting_jobs/01_slurm_submitting_jobs.md

Lines changed: 18 additions & 18 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
# Submitting Jobs on Torch
22

33
:::tip [Beginner tutorial available]
4-
If you are new to using HPC resources and would like to learn about the principles of using the `SLURM` scheduler for submitting batch jobs, please refer to cthis section](../13_tutorial_intro_hpc/04_scheduler_fundamentals.mdx). This section focuses on the specifics of the Torch cluster and assumes familiarity with the tutorial.
4+
If you are new to using HPC resources and would like to learn about the principles of using the `SLURM` scheduler for submitting batch jobs, please refer to [this section](../13_tutorial_intro_hpc/04_scheduler_fundamentals.mdx). This section focuses on the specifics of the Torch cluster and assumes familiarity with the tutorial.
55
:::
66

77

@@ -11,38 +11,38 @@ Instead of running interactive jobs on Login nodes, users can run interactive jo
1111

1212

1313
## Partition Management
14-
Partitions control stakeholder resource access.
15-
No physical nodes are tied to partitions — instead, equivalent compute resources are allocated via partition QoS.
16-
Jobs within the same partition cannot exceed their assigned resources (QOSGrpGRES).
17-
User GPU Quotas
18-
Each user has a total GPU quota of 24 GPUs for jobs with wall time < 48 hours (QOSMaxGRESPerUser).
14+
- Partitions control stakeholder resource access.
15+
- No physical nodes are tied to partitions — instead, equivalent compute resources are allocated via partition QoS.
16+
- Jobs within the same partition cannot exceed their assigned resources (QOSGrpGRES).
17+
- User GPU Quotas: Each user has a total GPU quota of 24 GPUs for jobs with wall time < 48 hours (QOSMaxGRESPerUser).
1918
## Job Submission
20-
Do not specify partitions manually.
21-
Only request the compute resources (e.g., GPUs, CPUs, memory).
22-
Scheduler will automatically dispatch jobs to all accessible GPU partitions that match resource requests.
19+
- Do not specify partitions manually.
20+
- Only request the compute resources (e.g., GPUs, CPUs, memory).
21+
- Scheduler will automatically dispatch jobs to all accessible GPU partitions that match resource requests.
2322

2423
:::warning [Low GPU Utilization Policy]
2524
Jobs with low GPU utilization will be automatically cancelled.
2625
The exact threshold is TBD, but enforcement will be very aggressive.
2726
:::
2827

29-
New Slurm configuration introduces preemption partitions enabling:
30-
Non-stakeholders to temporarily use stakeholder resources
31-
One stakeholder group to temporarily use another group’s resources
32-
Stakeholders retain normal access to their own resources.
33-
If non-stakeholders (or other stakeholders) are using them, their jobs may be preempted (cancelled) once stakeholders submit new jobs.
34-
Public users are allowed to use stakeholder resources only with preemption partitions.
28+
## New Slurm configuration introduces preemption partitions enabling:
29+
- Non-stakeholders to temporarily use stakeholder resources
30+
- One stakeholder group to temporarily use another group’s resources
31+
- Stakeholders retain normal access to their own resources.
32+
- If non-stakeholders (or other stakeholders) are using them, their jobs may be preempted (cancelled) once stakeholders submit new jobs.
33+
- Public users are allowed to use stakeholder resources only with preemption partitions.
3534

3635
:::info [Pre-Emption Policy]
3736
Jobs become eligible for pre-emption after 1 hour of runtime.
3837
Jobs will not be cancelled within the first hour.
38+
:::
3939

40-
How to Enable Pre-Emption
41-
To allow jobs in both normal and pre-emption partitions:
40+
## How to Enable Pre-Emption
41+
- To allow jobs in both normal and pre-emption partitions:
4242
#SBATCH --comment="preemption=yes;requeue=true"
4343
Jobs in stakeholder partitions will not be cancelled, but those in pre-emption partitions may be.
4444
Cancelled jobs will be requeued automatically with requeue=true
45-
To use only pre-emption partitions:
45+
- To use only pre-emption partitions:
4646
#SBATCH --comment="preemption=yes;preemption_partitions_only=yes;requeue=true"
4747
Jobs with preemption partitions only may be allowed to use more resources
4848

0 commit comments

Comments
 (0)