Campuses:
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| computing:department:unix:jobs:home [2009/01/29 19:21] – allan | computing:department:unix:jobs:home [2013/07/17 16:41] (current) – [I/O intensive jobs] allan | ||
|---|---|---|---|
| Line 5: | Line 5: | ||
| More about that on [[: | More about that on [[: | ||
| - | ==== Running Jobs on Unix ==== | + | ===== Running Jobs on Unix ===== |
| The best way to run background computing jobs on the unix systems is to submit them to the [[: | The best way to run background computing jobs on the unix systems is to submit them to the [[: | ||
| Line 14: | Line 14: | ||
| - | ==== Running Jobs Locally in the Background ==== | + | ===== Running Jobs Locally in the Background |
| If you're not using condor, then any non-interactive compute jobs should be //niced// - this reduces their priority level relative to interactive use, so that workstation users still have a responsive system. In the absence of interactive load, the system is still dedicated to your jobs, so in most cases runtime will not be much affected. | If you're not using condor, then any non-interactive compute jobs should be //niced// - this reduces their priority level relative to interactive use, so that workstation users still have a responsive system. In the absence of interactive load, the system is still dedicated to your jobs, so in most cases runtime will not be much affected. | ||
| Line 20: | Line 20: | ||
| If " | If " | ||
| + | # tcsh shell users: | ||
| nice +n yourprogram | nice +n yourprogram | ||
| + | |||
| + | # bash shell users: | ||
| + | nice -n yourprogram | ||
| where n is a number between 1 and 19 (the higher the number, the lower the job priority). | where n is a number between 1 and 19 (the higher the number, the lower the job priority). | ||
| Line 26: | Line 30: | ||
| You should choose the priority in the most socially-responsible way you can manage, according to how long you expect the job to run - eg, jobs which may run for days should be run at a lower priority than those which might only take a few hours. We also consider a priority of 4 to be the minimum socially-acceptable nice level to use for background jobs - so, for example: | You should choose the priority in the most socially-responsible way you can manage, according to how long you expect the job to run - eg, jobs which may run for days should be run at a lower priority than those which might only take a few hours. We also consider a priority of 4 to be the minimum socially-acceptable nice level to use for background jobs - so, for example: | ||
| + | # tcsh shell users: | ||
| nice +4 yourprogram | nice +4 yourprogram | ||
| + | # bash shell users: | ||
| + | nice -4 yourprogram | ||
| + | |||
| + | ===== I/O intensive jobs ===== | ||
| - | ==== I/O intensive | + | < |
| - | If your job requires manipulation of large files, it will be faster to use local scratch storage on the local machine rather than your home directory | + | If your job requires manipulation of large files (especially writing to them), it will be faster to use local scratch storage on the local machine rather than your home directory over the network. Check our pages on [[: |