skip to content
 

Ziggy is a cluster of eight dual-processor eight core Intel Xeon E5-2650  (with 128Gb RAM) nodes and sixteen dual-processor six core Intel Xeon X5650 (with 24Gb RAM) nodes. They all run Linux.

Ziggy can only be accessed by sshing into the head node, whose external name is ziggy.ch.cam.ac.uk. All work is done from there; there is no need to log into compute nodes. Ziggy uses the local Admitto service, so you log in with the same password as on the workstations.

Homespace is on a disk array attached to the head node. The /home filesystem is approximatately 1Tb in size and has user quotas which are currently set to 20Gb soft limit with a hard limit of 25Gb. /home is shared to all nodes on the cluster's internal network, so your job sees the same home directory wherever it is on the machine. It's important to remember that from a compute job's point of view accessing this directory is extremely slow, especially if all the nodes are trying at once. Compute jobs should always write data to a local disk if possible (/scratch), and copy it back to /home or /sharedscratch at the end.

There is also a shared scratch filesystem /sharedscratch in which you will have a directory. These are not backed up. They have a quota restriction of 250Gb soft limit and 300Gb hard limit, but it is expected that most people will stay well within that amount. They have the same speed issue as /home.

Each node also has a local /scratch filesystem on which the queueing system will create you a directory when you use the node. These filesystems are about 3.5T (ivybridge nodes) or 380G (westmere nodes) in size with no quota restriction and are the most appropriate place for your jobs to write temporary files during a run. They are local to each node and so considerably faster than the NFS-mounted /home and /sharedscratch. Please clean up files on /scratch when you are done with them; see the queueing documentation for how to find out which node's /scratch to look at. All of the node /scratch directories are accessible under /nodescratch on the head node. The system uses an automounter so the directories only appear when you try to access them. For example to see the /scratch from node compute-0-5 you need to type something like 'ls /nodescratch/compute-0-5'.

A variety of compilers and libraries are installed. Like most local Linux machines venus has the modules environment to allow you to switch between different compilers and libraries. The default environment is set up with all the available 64-bit compilers and Intel MPI. If you need to change this then use the module avail command to see what the other options are, and edit the version you want into your ~/.bash_profile file.

All compute jobs should be run through the queueing system as users cannot log directly into the nodes. The queueing system will run each job on a set of free compute nodes, copying the output back to a user-specified file at the end of the job. The queueing system is Torque/Maui; this will be familiar to users of the other theory sector clusters, but please note that the available queues are not the same on every machine. Read the generic instructions for instructions on how to use Torque and Ziggy's queueing setup for details of the queue setup if you already know Torque. The queueing configuration is always provisional and suggestions for improvements are warmly welcomed.

Can't find what you're looking for?

Then you might find our A-Z site index useful. Or, you can search the site using the box at the top of the page, or by clicking here.