Merge pull request #344 from NYU-RTS/max-jobs

added info on max jobs per user

Author: s-sajid-ali

docs/hpc/05_submitting_jobs/01_slurm_submitting_jobs.md

@@ -28,7 +28,7 @@ Non-stakeholders to temporarily use stakeholder resources (a stakeholder group t
 :::
 
 ## Job Submission on Torch
-As stated in the tuturial, always only request the compute resources (e.g., GPUs, CPUs, memory) needed for the job. Requesting too many resources can prevent your job from being scheduled within an adequate time. The `SLURM` scheduler will automatically dispatch jobs to all accessible GPU partitions that match resource requests.
+As stated in the tutorial, be sure to only request the compute resources (e.g., GPUs, CPUs, memory) needed for the job. Requesting too many resources can prevent your job from being scheduled within an adequate time. The `SLURM` scheduler will automatically dispatch jobs to all accessible GPU partitions that match resource requests.
 
 :::danger Low GPU Utilization Policy
 Jobs with low GPU utilization will be automatically canceled. The exact threshold is TBD, but enforcement will be very aggressive.

docs/hpc/06_tools_and_software/08_utils.mdx

@@ -107,6 +107,22 @@ As you can see above, `seff` gives information about CPU and memory efficiency t
 Requesting the minimum resources needed for your job can help it spend less time in the queue.
 :::
 
+## `show_slurm_qos`
+This shows the maximum number of cpus/gpus and memory allowed for different wall times.
+```bash
+[NetID@torch-login-b-0 ~]$ show_slurm_qos
+                    Name     MaxWall                MaxTRESPU    Preempt   PreemptExemptTime PreemptMode 
+------------------------ ----------- ------------------------ ---------- ------------------- ----------- 
+               cpu_short    06:00:00          cpu=32,mem=120G                                    cluster 
+                  cpu168  7-00:00:00       cpu=1000,mem=2000G                                    cluster 
+                   cpu48  2-00:00:00       cpu=3000,mem=6000G                                    cluster 
+                 cpuprem  2-00:00:00    cpu=30000,mem=120000G                                    cluster 
+                  gpu168  7-00:00:00               gres/gpu=4                                    cluster 
+                   gpu48  2-00:00:00              gres/gpu=16                                    cluster 
+             interactive    06:00:00           cpu=16,mem=60G                                    cluster
+```
+You can see that, in general, the partitions with shorter wall times will allow the use of greater resources.
+
 {/* coming soon
 ## `rpsquota`