Computer and Storage List
Computer List
name | office | user | cores | processor | RAM | OS | Video Ports | Displays | Q-Chem? |
---|---|---|---|---|---|---|---|---|---|
carpathia | 379 | Tests | 6 | Intel(R) Core(TM) i7-3930K CPU @ 3.20GHz | 32GB | Ubuntu 18.04.5 | |||
liminal | 379 | Alex | 6 | Intel(R) Core(TM) i7-7800X CPU @ 3.50GHz | 64GB | Ubuntu 18.04.5 | For FCIDUMPS: export QC=qclocal; . ~ajwt3/code/qchem/qcsetup.bash | ||
hypatia | 356 | Anna | 6 | Intel(R) Core(TM) i7-3930K CPU @ 3.20GHz | 32GB | Ubuntu 18.04.5 | |||
serenity | 378 | Andreea, César | 6 | Intel(R) Core(TM) i7-5930K CPU @ 3.50GHz | 64GB | Ubuntu 18.04 | |||
sandstone | 378 | Kripa | 6 | Intel(R) Core(TM) i7-5820K CPU @ 3.30GHz | 32GB | Ubuntu 20.04.4 | source /home/hynl2/code/qcsetup.bash | ||
gritstone | 145 | Brian | 6 | Intel(R) Core(TM) i7-5820K CPU @ 3.30GHz | 32GB | Ubuntu 18.04 | |||
moonraker | 145 | Nick Lee
Benjamin |
4 | Intel(R) Xeon(R) CPU E3-1270 v5 @ 3.60GHz | 64GB | Ubuntu 18.04.5 | export QC_EXT_LIBS=/home/hynl2/code/extlib; source /home/hynl2/.qcsetup | ||
obsidian | 145 | Lila, Isha, Zian | 6 | Intel(R) Core(TM) i7-6800K CPU @ 3.40GHz | 32GB | Ubuntu 18.04 | |||
hylas | 378 | Fabio | 6 | Intel(R) Core(TM) i7-6800K CPU @ 3.40GHz | 32GB | Ubuntu 18.04 | |||
cerberus | 379 | Alex | 6 | Intel(R) Core(TM) i7-5930K CPU @ 3.50GHz | 32GB | CentOS 7 [FPGA development board host] | |||
chucksty | 145 | David | 6 | Intel(R) Core(TM) i7-7800X CPU @ 3.50GHz | 64GB | Ubuntu 18.04 | |||
chesterian | 145 | Bang, Tarik | 6 | Intel(R) Core(TM) i7-7800X CPU @ 3.50GHz | 64GB | Ubuntu 18.04 | . /home/cbh31/code/qcsetup.public/qcselectversion.sh | ||
behemoth | 145 | Brian, Arta | 8 | Intel(R) Xeon(R) Silver 4208 CPU @ 2.10GHz | 256GB | Ubuntu 18.04.5 | |||
nemesis | 378 | Constance | 6 | Intel(R) Core(TM) i7-4930X CPU @ 3.40GHz | 16GB | Ubuntu 18.04.5 | |||
chiron | 360 | Chiara | 10 | Intel(R) Xeon(R) Silver 4210R CPU @ 2.40GHz | 96GB | Ubuntu 18.04.6 | |||
cerebro | Alavi & Thom Groups | 12 x 20
16 x 8 |
2x Intel(R) Xeon(R) CPU X5650 @ 2.67GHz
2x Intel(R) Xeon(R) CPU E5-2650 v2 @ 2.60GHz |
48GB
64GB |
Rocks 6.2 (CentOS 6.9) SLURM queuing | source /home/hynl2/.qcsetup | |||
CSD3 | University Tier-2 | 32 x 1152
56 x 672 |
2x Intel(R) Xeon Gold CPU 6142 @ 2.60GHz
2x Intel(R) Xeon Platinum CPU 8276 @ 2.20GHz |
192 or 384GB
192 or 384GB |
Scientific Linux release 7.9 (Nitrogen) SLURM queuing | source /rds/project/ajwt3/rds-ajwt3-thom1/qchem_public/qcsetup.bash | |||
nest | CUC3 Group cluster | 40 x 20 | 2x Cascade Lake Intel(R) Xeon Gold CPU 6248 @ 2.50GHz | 192GB | CentOS Linux release 7.9.2009 (Core) SLURM queuing | source /home/maf63/code/qcsetup.sh | |||
rogue | CUC3 Group cluster | (8 nVidia V100 + 32 CPU) x 2 | 2x Sky Lake Intel(R) Xeon Gold CPU 6130 @ 2.10GHz | 192GB | CentOS Linux release 7.9.2009 (Core) SLURM queuing | ||||
archer-2 | National Tier-1 Supercomputer | 128 x 5848 | 2 x AMD EPYC Zen2 (Rome) 64-core CPUs @ 2.2GHz | 256GB and 512GB |
Notes
To find out your OS version, run
lsb_release -a
To determine the RAM, run
head -1 /proc/meminfo
To find out core counts, run
cat /proc/cpuinfo
NB the number of 'processors' may be different from the number of cores owing to hyperthreading. The 'cpu cores' value is the one to take for single CPU machines.
Hobbit may also have some useful information.
Group computer reps can manage group entries in the department database and there's a hardware inventory and a space report too.
Storage
A common cause of running out of storage on your workstation is anaconda which puts stuff in /home. This can be safely moved to /scratch and a symbolic link.
cd $HOME mv .conda /scratch/$USER ln -s /scratch/$USER/.conda
Name | Type | Amount | Notes |
---|---|---|---|
/home/$USER | local disk | ~50Gb per person (changed to ~100GB after upgrade to 20.04) | Backed up with snapshots - Theory RIG policy |
/scratch/$USER | local disk | ~1Tb+ depending on computer | NOT BACKED UP |
/scratch/$USER/thom-fs-nethome
/scratch/$USER/thom-fs-common |
Chemistry network drive | 526Gb | Backed up with snapshots - Theory RIG policy |
/scratch/$USER/ifs-thom | UIS IFS mount | 6144Gb | Backed up with snapshots (24h+30d+12m)- avoid too much churn |
/scratch/$USER/theory-fs | Chemistry network drive | ~50Gb per person | Backed up with snapshots - Theory RIG policy |
cerebro:/filestore | Local RAID array | 36950Gb | Backed up with snapshots - Theory RIG policy |
Theory RIG backup policy
From https://www.ch.cam.ac.uk/computing/managed-linux-workstations-faq
have a few backups taken over the last 24 hours
then, about one backup per day for the previous week
then, about one backup per week for the previous month
then, about one backup per month for the previous few months