Differences

This shows you the differences between two versions of the page.

--- cluster:126 [2025/10/07 19:19] – hmeij07
+++ cluster:126 [2025/11/22 16:08] (current) – [In General] hmeij07
@@ Line 5: / Line 5: @@
 This page will be maintained and provide information to get users started using the compute cluster. It is a merger of the old "brief description" page and the "queue description" page.
+==== In General ====
+HPCC maintains and regularly updates an extensive software stack. Including provisioning tools, resource management, file transfer clients, development tools, a variety of scientific libraries, a variety of compilers (e.g. gcc/g++, OneAPI) and communication libraries (e.g., OpenMPI). Primarily provided by OpenHPC (https://openhpc.community/). Many opensource applications are custom compiled (about 100 or so used by many academic disciplines). The HPCC website offers documentation to help users resolve technical issues they may encounter (https://dokuwiki.wesleyan.edu/doku.php?id=cluster:0). Additional technical support (and tutors) is provided by the Scientific Computing and Informatics Center (https://www.wesleyan.edu/scic/) and the Quantitative Analysis Center (https://www.wesleyan.edu/qac/).
+ITS funds the system administrative support (0.75 FTE) of one ITS employee. Power and cooling are funded and maintained by Physical Plant. On an annual basis Academic Affairs contributes $25K and the HPCC users contribute $15K. This sets up a 4 year refresh cycle of $160K. On an annual basis Finance contributes up to $10K for maintenance (failed disks etc, monies do not roll over, use it or loose it).
+All HPCC hardware is located inside Wesleyan's ITS data center. Physical access is limited by swipe cards to certain ITS personnel. All head/login nodes (2 to 4 or so) are located on an internal subnet protected by Wesleyan's enterprise wide firewall. VPN is required from off campus. The internal HPCC network consists of two private subnets for the 100 or so compute nodes (one for job scheduler and monitoring tools, one for data transfers and NFS mounts). Access to HPCC resources is based on local Linux accounts and groups.
 ===== Description =====
@@ Line 53: / Line 61: @@
   * 10 nodes with dual 12 core chips (Xeon Silver 4410Y CPU @ 3.9 Ghz), Emerald Rapids Microway servers with a memory footprint of 256 GB (2,560 GB, about 90 teraflops dpfp). These nodes hold four RTX4070Ti-Super gpus each.  Known as the "desktop" racks. ''mwgpu256'', nodes 108-n117.
-  * 1 node with dual twelve core chips (Xeon Silver 4520, 2.40 Ghz) in ASUS ESC4000-E11 2U rack server with a memory footprint of 512 GB ( about 4 teraflops  dpfp). This node has four NVIDIA RTX PRO™ 6000 Blackwell Max-Q Workstation Edition  (96 GB memory footprint) gpus providing 440 teraflops (mixed mode). Known as the "Blackwell" gpu server, node n91, queue exx512, 48 job slots.
+  * 1 node with dual twelve core chips (Xeon Silver 4520, 2.40 Ghz) in ASUS ESC4000-E11 2U rack server with a memory footprint of 512 GB ( about 4 teraflops  dpfp). This node has four NVIDIA RTX PRO™ 6000 Blackwell Max-Q Workstation Edition  (96 GB memory footprint) gpus providing 440 teraflops (mixed mode). Known as the "Blackwell" gpu server, node n91, queue exx512, 48 job slots. [[https://www.techpowerup.com/gpu-specs/rtx-pro-6000-blackwell-max-q.c4273]]
 All queues are available for job submissions via cottontail2 login node. Some nodes on Infiniband switches for parallel computational jobs (queues: mw256fd, hp12, mw256).  Our total job slot count is roughly 2,672 with our physical core count 1,336. Our total teraflops compute capacity is about 92 cpu side and 2,902 gpu side (mixed mode). Our total memory footprint is about 1,584 GB gpu side and 13,524 GB cpu side.