Cedar/fr: Difference between revisions
(Updating to match new version of source page) |
No edit summary |
||
Line 1: | Line 1: | ||
<noinclude><languages /> | <noinclude><languages /> | ||
</noinclude> | |||
===GP2 (SFU)=== | ===GP2 (SFU)=== | ||
Revision as of 14:16, 17 November 2016
GP2 (SFU)
Introduction
L'évaluation du système GP2 n'est pas encore complétée en date du début novembre 2016. Les spécifications anticipées, basées sur l'appel d'offre et les offres reçues sont ci-dessous. Ces informations ne sont pas garanties et pourraient être incomplètes. Elles sont fournies dans une optique de planification.
Système de stockage
$HOME |
Standard home directory |
$SCRATCH Parallel High-performance filesystem |
Approximately 4PB usable capacity for temporary ( |
$PROJECT External persistent storage |
See below - 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 | 128GB of memory each |
"Large" compute nodes: | Over 100 nodes | 256GB of memory each |
"Bigmem512" | 24 nodes | 512 GB of memory each |
"Bigmem1500" nodes | 24 nodes | 1.5TB of memory each |
All of the above nodes will have 16 cores/socket (32 cores/node), with an anticipated frequency of 2.1Ghz.
"GPU base" nodes: | Over 100 nodes with 4 GPUs each. | 12 cores/socket (24 cores/node) with an anticipated frequency of 2.2Ghz. GPUs on a dual PCI root. |
"GPU large" nodes. | Approximately 30 nodes | same configuration as "GPU base," but a single PCI root. |
"Bigmem3000" nodes | 4 nodes | each with 3TB of memory. These are 4-socket nodes with 8 cores/socket. |
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.