Hammer
Hammer
Compute Resources
Link to section 'Overview of Hammer' of 'Overview of Hammer' Overview of Hammer
Hammer is optimized for Purdue's communities utilizing loosely-coupled, high-throughput computing. Hammer was initially built through a partnership with HP and Intel in April 2015. Hammer was expanded again in late 2016. Hammer will be expanded annually, with each year's purchase of nodes to remain in production for 5 years from their initial purchase.
To purchase access to Hammer today, go to the Cluster Access Purchase page. Please subscribe to our Community Cluster Program Mailing List to stay informed on the latest purchasing developments or contact us via email at rcac-cluster-purchase@lists.purdue.edu if you have any questions.
Link to section 'Hammer Specifications' of 'Overview of Hammer' Hammer Specifications
Most Hammer nodes consist of identical hardware. All Hammer nodes have variable numbers of processor cores, and 10 Gbps or 25 Gbps Ethernet interconnects.
| Front-Ends | Number of Nodes | Processors per Node | Cores per Node | Memory per Node |
|---|---|---|---|---|
| 2 | Two Sky Lake CPUs @ 2.60GHz | 48 (Logical) | 192 GB |
| Sub-Cluster | Number of Nodes | Processors per Node | Cores per Node | Memory per Node |
|---|---|---|---|---|
| F [000-012] | 13 | Two AMD EPYC 7702 @ 2GHz, one Nvidia Tesla T4 GPU | 256 | 512 GB |
| F [013-015] | 3 | Two AMD EPYC 7702 @ 2GHz | 256 | 512 GB |
| G | 6 | Two AMD EPYC 7702 @ 2GHz | 256 | 512 GB |
Hammer nodes run Rocky 8 and use Slurm (Simple Linux Utility for Resource Management) as the batch scheduler for resource and job management. The application of operating system patches occurs as security needs dictate. All nodes allow for unlimited stack usage, as well as unlimited core dump size (though disk space and server quotas may still be a limiting factor).
This compiler and these libraries are loaded by default. To load the recommended set again:
$ module load rcac
To verify what you loaded:
$ module list