You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/hpc/05_submitting_jobs/01_slurm_submitting_jobs.md
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -53,7 +53,7 @@ You can find the available types of GPUs at [Torch Spec Sheet](../10_spec_sheet.
53
53
Do not specify partitions manually, except for preemption which is described later.
54
54
:::
55
55
56
-
## Resource limits and restrictions
56
+
## Resource Limits and Restrictions
57
57
Jobs within the same partition cannot exceed their assigned resources (`QOSGrpGRES`). User GPU Quotas: Each user has a total GPU quota of 24 GPUs for jobs with wall time < 48 hours (`QOSMaxGRESPerUser`).
58
58
59
59
Non-stakeholders to temporarily use stakeholder resources (a stakeholder group to temporarily use another group’s resources). Stakeholders retain normal access to their own resources. If non-stakeholders (or other stakeholders) are using them, their jobs may be preempted (canceled) once stakeholders submit new jobs. Public users are allowed to use stakeholder resources only with preemption partitions. Refer to the section below for details on preemptible jobs.
@@ -81,7 +81,7 @@ Jobs with low GPU utilization will be automatically canceled:
81
81
Enforcement will be very aggressive.
82
82
:::
83
83
84
-
## Preemptible jobs on Torch
84
+
## Preemptible Jobs on Torch
85
85
On Torch, users may run "preemptible" jobs on stakeholder resources that their group does not own. This allows the stakeholder resources to be utilized by non-stakeholders which may otherwise be idle. To make the best use of these resources, you are encouraged to adopt checkpoint/restart to allow for resumption of the workload in subsequent jobs.
86
86
87
87
:::warning Preemption Policy
@@ -109,19 +109,19 @@ Jobs in stakeholder partitions will not be canceled, but those in preemption par
109
109
```
110
110
Jobs with preemption partitions only might be allowed to use more resources
111
111
112
-
## Advanced options
112
+
## Advanced Options
113
113
114
114
### GPU MPS
115
115
Use GPU Multi-Process Service (MPS) to improve overall GPU utilization, as this allows multiple GPU jobs to share a single GPU concurrently by:
116
116
```
117
117
#SBATCH --comment="gpu_mps=yes"
118
118
```
119
-
### RAM disk
119
+
### RAM Disk
120
120
A portion of the RAM available can be mounted as a disk for fast `I/O` operations:
121
121
```
122
122
#SBATCH --comment="ram_disk=1GB"
123
123
```
124
-
### GPU MPS & RAM Disk in a preemptible job
124
+
### GPU MPS & RAM Disk in a Preemptible Job
125
125
Both of these can be combined with preemption as shown:
0 commit comments