Differences

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

Link to this comparison view

Both sides previous revision Previous revision
Next revision		 Previous revision
Next revisionBoth sides next revision
doku:slurm [2023/03/14 12:15] – [Node configuration - hyperthreading] goldenbergdoku:slurm [2023/03/14 12:34] – [The job submission script] goldenberg
Line 25: Line 25:
 And the primary nodes of VSC-5 with: And the primary nodes of VSC-5 with:
 <code> <code>
-CoresPerSocket=24+CoresPerSocket=64
 Sockets=2 Sockets=2
 ThreadsPerCore=2 ThreadsPerCore=2
Line 41: Line 41:
  
 ==== Node allocation policy ==== ==== Node allocation policy ====
-On VSC-3 (as on VSC-2)  <html> <font color=#cc3300> only complete compute Nodes </font> </html>, i.e., integral multiples of 16 cores, can be allocated for user jobs. If you wish to run many single core jobs, there will be a possibility to schedule them in a smart way exploiting all 16 cpus of one node, please see the [[doku:slurm&#scheduler_script_for_many_single_core_jobs|scheduler script for a series of single core jobs]].+On VSC-4 there are a set of nodes which accept jobs that do not require entire nodes (anythong from 1 core to less than a full node). These nodes are set up to accomodate different jobs from different users until they are full. They are automatically used for such types of jobs. All other nodes are assigned completely to a job.  
 +On VSC-5 that feature is not yet active, so only complete nodes are assigned to jobs.
  
  
Line 54: Line 55:
 ==== The job submission script==== ==== The job submission script====
  
-It is recommended to write the job script using a [[doku:win2vsc&#the_job_filetext_editors_on_the_cluster|text editor]] on the VSC //Linux// cluster. +It is recommended to write the job script using a [[doku:win2vsc&#the_job_filetext_editors_on_the_cluster|text editor]] on the VSC //Linux// cluster or on any Linux/Mac system. 
 Editors in //Windows// may add additional invisible characters to the job file which render it unreadable and, thus, it is not executed.  Editors in //Windows// may add additional invisible characters to the job file which render it unreadable and, thus, it is not executed. 
  
Line 63: Line 64:
 #SBATCH -J chk #SBATCH -J chk
 #SBATCH -N 2 #SBATCH -N 2
-#SBATCH --ntasks-per-node=16+#SBATCH --ntasks-per-node=48
 #SBATCH --ntasks-per-core=1 #SBATCH --ntasks-per-core=1
 #SBATCH --mail-type=BEGIN    # first have to state the type of event to occur  #SBATCH --mail-type=BEGIN    # first have to state the type of event to occur 
Line 70: Line 71:
 # when srun is used, you need to set: # when srun is used, you need to set:
  
-<srun -l -N2 -n32 a.out > +<srun -l -N2 -n96 a.out > 
 # or # or
-<mpirun -np 32 a.out>+<mpirun -np 96 a.out>
 </code> </code>
   * **-J**     job name,\\    * **-J**     job name,\\ 
Line 84: Line 85:
   * **--mail-user** sends an email to this address   * **--mail-user** sends an email to this address
  
-In order to send the job to specific queues, see [[doku:vsc3_queue|Queue/Partition setup on VSC-3]].+In order to send the job to specific queues, see [[doku:vsc4_queue|Queue | Partition setup on VSC-4]] or [[doku:vsc5_queue|Queue | Partition setup on VSC-5]].
 ====Job submission==== ====Job submission====
    
  • doku/slurm.txt
  • Last modified: 2024/02/07 10:55
  • by katrin