Best practices for job submission: Difference between revisions

Best practices for job submission (view source)

Revision as of 17:32, 2 September 2022

5 bytes removed , 2 years ago

Removed one bullet level

Plstonge

cc_staff

782

edits

@@ Line 12: / Line 12: @@
 =Best practice tips=
-* The best approach is to begin by submitting a few relatively small test jobs, asking for a fairly standard amount of memory (<tt>#SBATCH --mem-per-cpu=2G</tt>) and time, for example one or two hours.
+The best approach is to begin by submitting a few relatively small test jobs, asking for a fairly standard amount of memory (<tt>#SBATCH --mem-per-cpu=2G</tt>) and time, for example one or two hours.
-** Ideally you should already know what the answer will be in these test jobs, allowing you to verify that the software is running correctly on the cluster.
+* Ideally you should already know what the answer will be in these test jobs, allowing you to verify that the software is running correctly on the cluster.
-** If the job ends before the computation finished, you can increase the duration by doubling it until the job's duration is sufficient.
+* If the job ends before the computation finished, you can increase the duration by doubling it until the job's duration is sufficient.
-** If your job ends with a message about an "OOM event" this means it ran out of memory (OOM), so try doubling the memory you've requested and see if this is enough.
+* If your job ends with a message about an "OOM event" this means it ran out of memory (OOM), so try doubling the memory you've requested and see if this is enough.
 By means of these test jobs, you should gain some familiarity with how long certain analyses require on the cluster and how much memory is needed, so that for more realistic jobs you'll be able to make an intelligent estimate.