This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
quick:loadshedding [2022/07/15 12:37] alopis [1. Prioritise your most urgent jobs.] |
quick:loadshedding [2022/07/15 13:31] (current) wikiadmin |
||
|---|---|---|---|
| Line 43: | Line 43: | ||
| ====5. Testing of a new type of job/ | ====5. Testing of a new type of job/ | ||
| - | 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, | + | When testing a new job script, either use an [[quick: |
| ====6. Check how well your job is running. ==== | ====6. Check how well your job is running. ==== | ||
| Always check to see if your job is working correctly: | Always check to see if your job is working correctly: | ||
| - Is it producing the expected output at the expected rate? | - Is it producing the expected output at the expected rate? | ||
| - | - Are you fully using all the compute cores that you requested? | + | - 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 '' | ||
| So to determine which node number/s your job is using: | So to determine which node number/s your job is using: | ||
| - | qstat -u yourusername -n1 | + | qstat -u yourusername -n |
| Then ssh into this node/s, for example | Then ssh into this node/s, for example | ||