Using the IRIDIA Cluster
Currently the IRIDIA cluster is composed by two racks. The first one contains 1 server (majorana) + 32 computational nodes (from c0-0 to c0-31), while the second contains 16 computational nodes (from c1-0 to c1-15). Each of the older units (from c0-0 to c0-31) features 2 CPUs AMD Opteron 244 (each with 1MB L2 cache) working at 1,75GHz and 2GB of RAM. Nodes from c0-0 to c0-15 have 4 modules of 512MB 400MHz DDR ECC REG DIMM. Nodes from c0-16 to c0-31 have 8 modules of 256MB 400MHz DDR ECC REG DIMM. Each of the newer units (from c1-0 to c1-15) features 2 Dual-Core AMD Opteron Processors 2216 HE (each with 2x1MB L2 cache) working at 2,4GHz and 4GB of RAM. In total the cluster is composed of 96 CPUs (64 single-core + 32 dual-core) dedicated to computations and 2 CPUs for administrative purposes.
- 2 Single-Core AMD Opteron244 @ 1,75GHz
nodes: c0-0, c0-1, c0-2, c0-3, c0-4, c0-5, c0-6, c0-7, c0-8, c0-9, c0-10, c0-11, c0-12, c0-13, c0-14, c0-15, c0-16, c0-17, c0-18, c0-19, c0-20, c0-21, c0-22, c0-23, c0-24, c0-25, c0-26, c0-27, c0-28, c0-29, c0-30, c0-31
- 2 Dual-Core AMD Opteron2216 HE @ 2,4GHz
nodes: c1-0, c1-1, c1-2, c1-3, c1-4, c1-5, c1-6, c1-7, c1-8, c1-9, c1-10, c1-11, c1-12, c1-13, c1-14, c1-15
|c0-0||offline||13 Jul 07||cpu-fan broken|
|c0-1||offline||11 Jul 07||disk not seen by bios|
|c0-2||offline||10 Oct 07||disk not seen by bios|
|c0-3||offline||10 Oct 07||disk not seen by bios|
|c0-4||offline||24 Aug 07||disk not seen by bios|
|c0-9||offline||24 Aug 07||node reboot|
|c0-24||offline||13 Jul 07||power supply broken|
Each computational node the following queues, one per each core:
- <node>.short: jobs run in this queue at nice-level 2 for maximum 24h of CPU time (real execution of the program, without counting the time needed by the system for multitasking, etc). If a job still runs after the 24th hour, it will receive a signal SIGUSR1 and after some more time a SIGKILL that will terminate it.
- <node>.medium: jobs run in this queue at nice-level 3 (lower priority than the short ones) for maximum 72h of CPU time (real execution of the program, without counting the time needed by the system for multitasking, etc). If a job still runs after the 72nd hour, it will receive a signal SIGUSR1 and after some more time a SIGKILL that will terminate it.
- <node>.long: jobs run in this queue at nice-level 3 (lower priority than the short ones) for maximum 168h of CPU time (real execution of the program, without counting the time needed by the system for multitasking, etc). If a job still runs after the 168th hour, it will receive a signal SIGUSR1 and after some more time a SIGKILL that will terminate it.
Summarizing: on each node can run concurrently up to 3 jobs per core with an average space in RAM of 341MB per job.
YOU HAVE TO DESIGN YOUR COMPUTATIONS IN SUCH A WAY THAT EACH SINGLE JOB DOESN'T RUN FOR MORE THAN 7 DAYS (of CPU time).
How to submit a job
To submit a job you have to create a script (that we indicate with SCRIPT_NAME.sh) with the commands you want to execute. Once you have the script, from majorana execute the command qsub SCRIPT_NAME.sh
The script should begin like this:
#!/bin/bash #$ -N NAME_OF_JOB #$ -cwd
In this case the job will be scheduled for execution in one node chosen from any node in one queue chosen from any queue of that node.
If you want, you can impose some restrictions on the kind of node or queue to choose from.
To select a node with Opteron 244 CPUs, you must add to your script the line #$ -l opteron244, while to select a node with Opteron 2216 CPUs, you must add to your script the line #$ -l opteron2216. To select only among the short queues, you must add to your script the line #$ -l short; to select only among the medium queues, you must add the line #$ -l medium; to select only among the long queues, you must add to your script the line #$ -l long.
THE SCHEDULER CANNOT PUT IN EXECUTION MORE THAN 64 JOBS OF THE SAME USER AT THE SAME TIME. IF YOU SUBMIT MORE THAN 64 JOBS, MAXIMUM 64 WILL BE RUNNING AT THE SAME TIME.
Submission tips for the cluster
If your job lasts less than 1 day it doesn't matter in which queue it will end up because no time constraint will be violated. In this case you might want that it gets the first queue available, no matter which. To do so, simply remove the -l queue_name from your script.
Programming tips for the cluster
If the jobs needs to read/write quite much and often, in the submission script it is better to copy the input files to the /tmp directory (which is in the local harddrive of the node) and to write the output files also there, moving them in the /home/user_name directory only when the computation is over. In this way your job does not have to use NFS for each read/write operation relieving majorana of some weight (the /home partition is exported from there to all the nodes), making it more fast.
REMEMBER TO REMOVE YOUR FILES FROM THE /TMP DIRECTORY ONCE THE COMPUTATION IS OVER