Cedar/en: Difference between revisions
(Updating to match new version of source page) |
|||
Line 64: | Line 64: | ||
====Name==== | ====Name==== | ||
For naming details of the new systems see [[Migration2016:New_System_Names]]. | For naming details of the new systems see [[Migration2016:New_System_Names]]. | ||
<noinclude> | <noinclude> | ||
</noinclude> | </noinclude> |
Revision as of 18:48, 22 November 2016
GP2 (SFU)
Introduction
The GP2 system evaluation is not yet completed (as of early November 2016). Anticipated specifications, based on SFU's RFP and bids received, include the following. This information is not guaranteed and might not be complete. It is provided for planning purposes.
Attached Storage System
$HOME |
Standard home directory |
$SCRATCH Parallel High-performance filesystem |
Approximately 4PB usable capacity for temporary ( |
$PROJECT External persistent storage |
Provided by the NDC. |
High performance interconnect |
Low-latency high-performance fabric connecting all nodes and temporary storage. |
Node types and characteristics:
"Base" compute nodes: | Over 500 nodes | 128 GB of memory, 16 cores/socket, 2 sockets/node |
"Large" compute nodes: | Over 100 nodes | 256 GB of memory, 16 cores/socket, 2 sockets/node |
"Bigmem512" | 24 nodes | 512 GB of memory, 16 cores/socket, 2 sockets/node |
"Bigmem1500" nodes | 24 nodes | 1.5 TB of memory, 16 cores/socket, 2 sockets/node |
"GPU base" nodes: | Over 100 nodes | 128 GB of memory, 12 cores/socket, 2 sockets/node, 4 GPUs/node, 2 GPUs/socket. |
"GPU large" nodes. | Approximately 30 nodes | 256 GB of memory, 12 cores/socket, 2 sockets/node, 4 GPUs/node, All GPUs on the same socket |
"Bigmem3000" nodes | 4 nodes | 3 TB of memory, 8 cores/socket, 4 sockets/node |
All of the above nodes will have local (on-node) storage.
Compute Canada is not currently able to disclose the specific GPU model or specifications. The RFP used NVIDIA K80 as a baseline specification.
The total GP2 system is anticipated to have over 25,000 cores, 900 nodes, and 500 GPUs.
The delivery and installation schedule is not yet known, but the procurement team has confidence that the system will be in production for the start of the allocations year on April 1, 2017.
Name
For naming details of the new systems see Migration2016:New_System_Names.