Differences

This shows you the differences between two versions of the page.

--- tools:slurm [2024/04/24 12:02] – [Slurm options] will
+++ tools:slurm [2026/05/19 16:27] (current) – [sbatch options] will
@@ Line 19: / Line 19: @@
-===== ''sbatch'' options =====
+===== sbatch options =====
 Jobs are submitted with options given to ''sbatch''. Here's a subset of important options:
@@ Line 26: / Line 26: @@
   * ''--time hh:mm:ss'' : maximum run time for your job. On RM-shared, the max run time appears to be 48:00:00. If the partition you are requesting is full/backed up, jobs with shorter run times are prioritized over those with longer requested times
   * ''--nodes'' : The number of nodes to use. Typically 1 is sufficient (and appears to be the max you can request on RM-shared)
-  * ''--ntasks-per-node'' : The number of cores to use per node. Importantly, increasing the number of cores requested increases your job's memory (RAM) allocation. On RM-shared, each core comes with 1.95G memory. So four nodes e.g. will get you 7.81 GB
+  * ''--ntasks-per-node'' : The number of cores to use per node. Importantly, increasing the number of cores requested increases your job's memory (RAM) allocation. On [[:tools:PSC]]'s ''RM-shared'' partition, each core comes with 1.95G memory. So four nodes e.g. will get you 7.81 GB. See [[https://www.psc.edu/resources/bridges-2/user-guide/#:~:text=specifically%20request%20memory.%20jobs%20are%20alloted%202gb%20of%20memory%20per%20core%20that%20is%20requested.%20|PSC user guide "RM-shared partition" section]]
   * ''-n'' : number of cores requested in total (useful if you are requesting >1 node and dividing requested cores over nodes)
   * ''-J "$subid-$script"'' : The name of your job. By default, jobs are named by their job id, however you can customize the job name via variables like $subid