Until now I didn’t know how many cores I had to work on. The info in /proc/cpuinfo just didn’t seem to tie in with what the vendor had supplied. Then the penny dropped, /proc/cpuinfo only tells you about the current node, while I wanted to find out about the whole cluster. OK, seems obvious now, but here is some useful info I collected along the way.
One thing I haven’t found is how to find out how many nodes (hosts) are in your local domain?
1. A “chassis” houses one or more nodes.
2. A node contains one or more sockets.
3. A socket holds one processor.
4. A processor contains one or more (CPU) cores.
5. The cores perform FLOPS.
||List processor information. Each physical chip has a unique ““physical id”. Cores of the same chip have the same physical ID but different core ids.
This will only tell you about the local node! You will need to SSH into other nodes to work out about them as well.
Useful AWK script here:
The head node on my cluster has two sockets, with quad core chips, but with hyperthreading enabled, so that it looks like 16 logical ‘processors’. The calculation nodes also have two sockets, with quad core CPUS, so 8 cores per node. In total I have 216 calculation cores to play with!