- Infos im HLRS Wiki sind nicht rechtsverbindlich und ohne Gewähr -
- Information contained in the HLRS Wiki is not legally binding and HLRS is not responsible for any damages that might result from its use -
HPE Hawk: Difference between revisions
No edit summary |
|||
| Line 6: | Line 6: | ||
The information below applies to the Test and Development System (TDS) which is similar to the future Hawk production system. Please have in mind that this is a system under construction. Hence modifications might occur ''without'' announcement and stuff may not work as expected from time to time! | The information below applies to the Test and Development System (TDS) which is similar to the future Hawk production system. Please have in mind that this is a system under construction. Hence modifications might occur ''without'' announcement and stuff may not work as expected from time to time! | ||
| Line 19: | Line 13: | ||
* [https://developer.amd.com/wp-content/resources/56255_3_03.PDF Open-Source Register Reference for AMD EPYC Rome Processors] <br> (in particular describing available hardware performance counters) | * [https://developer.amd.com/wp-content/resources/56255_3_03.PDF Open-Source Register Reference for AMD EPYC Rome Processors] <br> (in particular describing available hardware performance counters) | ||
* [https://www.amd.com/system/files/TechDocs/47414_15h_sw_opt_guide.pdf Software Optimization Guide for AMD Family 15h] <br> (although depicting an older family of AMD processors, the optimization approaches shown in this document are also applicable to the AMD EPYC Rome processor deployed in Hawk) | * [https://www.amd.com/system/files/TechDocs/47414_15h_sw_opt_guide.pdf Software Optimization Guide for AMD Family 15h] <br> (although depicting an older family of AMD processors, the optimization approaches shown in this document are also applicable to the AMD EPYC Rome processor deployed in Hawk) | ||
'''MPI''': | |||
* [http://www.hpe.com/support/mpi-ug-036 HPE Message Passing Interface (MPI) User Guide] | |||
<br> | <br> | ||
== Access == | |||
Login-Node: hawk-tds-login1.hww.hlrs.de | |||
{{note|text=Access to the Hawk TDS is possible now on request. In case you have early access, we ask you to provide us with your experience regarding usage and performance (approximately half a page) once a month.}} | |||
<br> | <br> | ||
== Module environment == | == Module environment == | ||
Revision as of 12:18, 4 February 2020
If your job does not start, please have in mind the time-dependent limitations according to Batch System!
This Page is under construction!
The information below applies to the Test and Development System (TDS) which is similar to the future Hawk production system. Please have in mind that this is a system under construction. Hence modifications might occur without announcement and stuff may not work as expected from time to time!
Manuals
Processor:
- Software Optimization Guide for AMD EPYC Rome Processors
- Open-Source Register Reference for AMD EPYC Rome Processors
(in particular describing available hardware performance counters) - Software Optimization Guide for AMD Family 15h
(although depicting an older family of AMD processors, the optimization approaches shown in this document are also applicable to the AMD EPYC Rome processor deployed in Hawk)
MPI:
Access
Login-Node: hawk-tds-login1.hww.hlrs.de
Module environment
Compiler
MPI
Tuned MPI: In order to use the MPI implementation provided by HPE, please load the Message Passing Toolkit (MPT) module mpt (not ABI-compatible to other MPI implementations) or hmpt (ABI-compatible to MPICH-derivatives).
User Guide: For detailed information cf. the HPE Message Passing Interface (MPI) User Guide.
Performance optimization: With respect to MPI performance optimization by means of tuning environment variables please cf. Tuning of MPT
Interconnect topology: Hawk deploys an Infiniband HDR based interconnect with a 9-dimensional enhanced hypercube topology. Please refer to here with respect to the latter. Infiniband HDR has a bandwidth of 200 Gbit/s and a MPI latency of ~1.3us per link. The full bandwidth of 200 Gbit/s can be used if communicating between the 16 nodes connected to the same node of the hypercube (cf. here). Within the hypercube, the higher the dimension, the less bandwidth is available.
Libraries
Disk storage
Home directories as well as workspaces are handled in the same way as on Hazel Hen, so please cf. Storage Description regarding details.
Batch System
Best Practises for Software Installation
Best practices for software installation on Hawk is described on a separate (internal) wiki page Software Installation on Hawk.