Best practices for job submission: Difference between revisions

Jump to navigation Jump to search
no edit summary
No edit summary
No edit summary
 
Line 21: Line 21:


<!--T:6-->
<!--T:6-->
The best approach is to begin by submitting a few relatively small test jobs, asking for a fairly standard amount of memory (<>#SBATCH --mem-per-cpu=2G</code>) 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 (<code>#SBATCH --mem-per-cpu=2G</code>) 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.
rsnt_translations
57,772

edits

Navigation menu