Differences

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

--- quick:loadshedding [2022/07/15 12:19]
ccrosby [5. Testing of a new type of job/calculation]
+++ quick:loadshedding [2022/07/15 13:31] (current)
wikiadmin
@@ Line 15: / Line 15: @@
 ====1. Prioritise your most urgent jobs.====
-Please plan your work so that only the most urgently needed jobs are submitted.  Making your workflow more efficient will help you make more effective use of the cluster.
+Please plan your work so that only the most urgently needed jobs are submitted.  Making your workflow more efficient will help you make more effective use of the cluster. Please be cautious and check you've set up your job correctly.
@@ Line 41: / Line 41: @@
 Breaking a very long running job into shorter job runs using checkpoints will help with queuing times. If you already use checkpoints, it will help if you increase the frequency of checkpoint file outputs when possible, to submit shorter jobs.
-====5. Testing of a new type of job/calculation====
+====5. Testing of a new type of job/calculation. ====
-When testing a new job script, either use an interactive job, on a single node, or a very very short job (maybe 15 mins). This way you will know your job will work, and then you can submit your actual longer job thereafter. You can thus avoid waiting hours or even days to find your job failed, due to perhaps a small error in your input file. Most importantly, **test!**  Please read our section on [[howto:tipsandtricks#please_slow_down_and_work_methodically|working methodically]].
+When testing a new job script, either use an [[quick:start#example_interactive_job_request| interactive job]], on a single node, or a very very short job (maybe 15 mins). This way you will know your job will work, and then you can submit your actual longer job thereafter. You can thus avoid waiting hours or even days to find your job failed, due to perhaps a small error in your input file. Most importantly, **test!**  Please read our section on [[howto:tipsandtricks#please_slow_down_and_work_methodically|working methodically]].
+====6. Check how well your job is running. ====
+Always check to see if your job is working correctly:
+  - Is it producing the expected output at the expected rate?
+  - Are you fully using all the compute cores that you requested?
+You can ssh into your assigned nodes once your job has started running and monitor activity with ''top'' or ''htop''.
+So to determine which node number/s your job is using:
+  qstat -u yourusername -n
+Then ssh into this node/s, for example
+  ssh cnode0123
+  htop

wiki.chpc.ac.za

User Tools

Site Tools

Differences

Page Tools