Changes between Version 67 and Version 68 of cypress/using

Timestamp:

11/22/22 16:29:17 (17 months ago)

Author:

fuji

Comment:

—

cypress/using

@@ -407 +407 @@
 * '''afterok:jobid[:jobid...]'''        job can begin after the specified jobs have run to completion with an exit code of zero (see the user guide for caveats).
 
-See [https://wiki.hpc.tulane.edu/trac/wiki/Workshops/cypress/JobDependency here] for more about job-dependency.
+See [https://wiki.hpc.tulane.edu/trac/wiki/Workshops/cypress/JobDependency here] for more about job dependency.
+
+=== Many-task computing ===
+If you have many tasks and each task needs a few cores, it may be beneficial to pack several tasks into one job.
+For example,
+
+{{{
+#!/bin/bash
+#SBATCH --qos=normal            # Quality of Service
+#SBATCH --job-name=many-task    # Job Name
+#SBATCH --time=24:00:00         # WallTime
+#SBATCH --nodes=1               # Number of Nodes
+#SBATCH --ntasks-per-node=1     # Number of tasks (MPI presseces)
+#SBATCH --cpus-per-task=20      # Number of processors per task OpenMP threads()
+
+# Our custom function
+cust_func(){
+  echo "Do something $1 task"
+  sleep 1
+}
+# For loop 20 times
+date
+for i in {1..20}
+do
+        cust_func $i & # Put a function in the background
+done
+
+## Put all cust_func in the background and bash
+## would wait until those are completed
+## before displaying all done message
+wait
+echo "All done"
+date
+}}}
+
+See [https://wiki.hpc.tulane.edu/trac/wiki/Workshops/cypress/ManyTaskComputing here] for more about Many Task Computing.
+
 
 == Submitting Interactive Jobs ==