The Duke Compute Cluster
The Duke Compute Cluster (formerly called the Duke Shared Cluster Resource or “DSCR”) consists of machines that the University has provided for community use and that researchers have purchased to conduct their research. At present, the cluster consists of more than 460 nodes, mostly Dell M600-series blades in Dell M1000-series chassis. Thus, the cluster itself is a project of the University community, with the hardware provided by individual researchers and the University. The University, through Duke Research Computing and the Office of Information Technology, maintains and administers the equipment for its useful life (designated to be four years) and provides support for cluster users. As a result of the incremental purchases, the cluster is heterogeneous, with a narrow range of Intel chipsets and RAM capacities, though purchases of equipment are organized and channeled by Duke Research Computing in order to ease maintenance and exploit economies of scale. New nodes have 256 GB of RAM (Dell is the current designate vendor for blades), though researchers have purchased nodes with RAM up to 512 GB.
Researchers who have provided equipment have “high priority” access to their nodes and have “low priority” (or “common”) access to others' nodes, including those purchased by the University, when idle cycles are available. Since researchers tend not to use 100 percent of the CPU of nodes they have purchased, “low priority” consumption of cycles greatly increases the efficiency of the cluster overall, while also providing all users the benefit of being able to access more than their own nodes' cycles when they might need it. Jobs submitted with high priority run only on the nodes that members have bought, and low priority jobs on the machines yield to high priority jobs.
The Duke Compute Cluster is a general purpose high performance/high-throughput installation, and it is fitted with software used for a broad array of scientific projects. For the most part, applications on the cluster are Free and Open Source Software (FOSS), though some researchers have arranged for proprietary licenses for software they use on the cluster. The operating system and software installation and configuration is standard across all nodes (barring license restrictions), with Red Hat Enterprise Linux 6 the current operating system. SLURM is the scheduler for the entire system. The entire system is professional managed by systems administrators in the Office of Information Technology and the equipment is housed in enterprise-grade data centers on Duke's West Campus. Software installations and user support, including training on using the system, is provided by experienced staff of Duke Research Computing.
Accessing the Duke Compute Cluster
There are currently 2 "front-end" machines that users must login to first. The names of these head nodes are dscr-slogin-01.oit.duke.edu and dscr-slogin-02.oit.duke.edu. There is also a dedicated file-transfer node, dscr-xfer-01.oit.duke.edu, that has higher-speed networking capabilities to help get data in and out of the cluster faster (but it will only accept sftp; ssh logins will not work on dscr-xfer-01).
Once you are logged in to a front-end, you will be able to login from there to any node in the cluster. Most of your work will be done on the front-ends: compilation, job submission, debugging. The only time you may need to directly login to any node is for parallel debugging.
To learn more about gaining access to the Duke Compute Cluster, please see Gaining Access.
If you are a member of a group that already participates in the DSCR, please direct your new account request through your designated Point Of Contact
- New: SLURM Queueing System
- Installed Applications
- Using the Cluster
- SGE Queueing System
- Compilers and Libraries
- MPICH Parallel Library
- Machine Info
- Status Monitoring
- Storage Usage
- CPU Speed Issues
- CSH Scripting Basics
- Other References
- Scripted Remote Access to the cluster
- Searching the DSCR Documentation
For more information, you can email us at hpc-support at duke.edu