At CPSNet, we operate under the honor system when it comes to submitting jobs. We have no central batch processing system in place. Instead we ask that users take control of their resources while paying attention to the needs of others users and not hogging precious resources.
For users running large jobs or requiring large repositories for data storage, you should consult Luis Cruz-Cruz about getting an account at the University SuperComputer facility or space on our RAID array.
When submitting a job to machines on the CPSNet cluster, the first step to submitting a job is to see which machine to submit to. The following is a list of machines, OS, and the maximum number of jobs per machine.
| Machine Name | OS | Memory/Virtual Memory | Architecture | Max Jobs | PS command |
|---|---|---|---|---|---|
| linda | SGI Irix | 1.256G/2.5G | Dual 64bit MIPS R10000 | 2 | ps -aef |
| yanko | Linux | 1G/2G | Dual 600Mhz Pentium III | 2 | ps -aef |
| water, thalia, riskit, jhilad, urania, luna, melete, vesta, pan, rushmore, hypate | Linux | 512M/1G | Dual 750Mhz Pentium III | 2 | ps -aef |
| macduff,trantor,daneel | SGI Irix | 96M/256M | 64bit MIPS R4000 | 1 | ps -aef |
| ceres,juno,risa,darmok,hober | DEC OSF/1 | 256M/512M | 64bit Alpha 500MHZ | 1 | ps guaxw |
NOTE 1: A maximum of TEN jobs per user may be running at any given time.
NOTE 2: You cannot submit jobs to the following machines: META, ARGENTO, BAILEY, ARKADY, DUNCAN, and IRIS.
These rules MUST be strictly adhered to.
You can find out how many jobs are running by running the 'top' command, and then looking at the list of processes. Jobs should be submitted with names file.out so that it is easy to spot jobs.
You may also wish to use the script jobchk to check jobs automatically across all machines. To use this script, follow the following steps:
cd mkdir bin cp /users/meta/jobchk bin/. source .login rehash
Once the script is installed, you can invoke it by typing:
jobchk
You should check to see what the load is on the various machines and can opt to not to submit a job to machines with high loads because your program will run slow. You should also be aware the there may be processes listed that are NOT actual jobs since the script searches for jobs with .out or .exe in its name. So, netscape.exe would come up as a "job" even though it is not really the type of job you are looking for. For convention, you should submit all jobs with names ending in .out.
If your job requires a lot of memory to run then you should check the free memory available in the machine that you plan to run. The free memory is listed when running 'top'.
Once you have determined the machine to submit to (you have checked the number of jobs and memory requirements), you are now ready to run the job in the background. You must always submit the job using nice, this is required so that your job does not take over the machine. Submit a job by logging into the machine you wish to submit and typing:
nice program-name.out &