Facility | Comet |
---|---|
Facility Status | Planning |
Node Type | Standard.b |
Node Quantity | 36 |
RAM | 1152 GBytes |
CPU | 2x CPU : AMD EPYC 9745 (x86_64) |
GPU | - |
Reserved | 20% for unfunded use |
Reserved | 80% for funded use |
CPU Vendor | AMD |
---|---|
CPU Model | EPYC 9745 |
CPU Architecture | x86_64 |
CPU Cores | 128 |
CPU Threads | 256 |
Base Frequency | 2400MHz |
Turbo Frequency | 3700MHz |
Cache (L1) | 6144 KBytes |
Cache (L2) | 131072 KBytes |
Cache (L3) | 256 MBytes |
Standard compute node as found in the Comet HPC facility. This node is meant for non low-latency jobs running via MPI, as it is connected via a standard (albeit high-speed) ethernet network.
For low latency jobs that communicate whilst running, we have dedicated low latency nodes.
All registered users of the Comet facility may access any of the hours of compute available in the unfunded queues, as listed below. However, your jobs may need to wait longer to run due to the number of resources available. Consider building in costing for your research activity or project for dedicated HPC resources to enable access to the larger pool of resources dedicated for funded queues.
The maximum hours of CPU compute available across all users of unfunded queues is:
(36 Nodes) x (2 Processors) x (128 Cores) x (730 Hours/Month) x (20%) = 1345536.0 Compute Hours/Month
The maximum hours of CPU compute available across all users of funded queues is:
(36 Nodes) x (2 Processors) x (128 Cores) x (730 Hours/Month) x (80%) = 5382144.0 Compute Hours/Month
You can use the for the Comet facility to model the potential contributions towards accessing these resources.
Note: You must be logged in to access the costing tool.