SAP-C02 · Question #502
A company has built a high performance computing (HPC) cluster in AWS for a tightly coupled workload that generates a large number of shared files stored in Amazon EFS. The cluster was performing…
The correct answer is A. Ensure the HPC cluster is launched within a single Availability Zone. C. Select EC2 instance types with an Elastic Fabric Adapter (EFA) enabled. F. Replace Amazon EFS with Amazon FSx for Lustre. To achieve maximum performance for a large, tightly coupled HPC cluster with shared files, launch it within a single Availability Zone, select EC2 instances with Elastic Fabric Adapter (EFA), and replace Amazon EFS with Amazon FSx for Lustre for high-performance shared storage.
Question
A company has built a high performance computing (HPC) cluster in AWS for a tightly coupled workload that generates a large number of shared files stored in Amazon EFS. The cluster was performing well when the number of Amazon EC2 instances in the cluster was 100. However, when the company increased the cluster size to 1.000 EC2 instances, overall performance was well below expectations. Which collection of design choices should a solutions architect make to achieve the maximum performance from the HPC cluster? (Choose three.)
Options
- AEnsure the HPC cluster is launched within a single Availability Zone.
- BLaunch the EC2 instances and attach elastic network interfaces in multiples of four.
- CSelect EC2 instance types with an Elastic Fabric Adapter (EFA) enabled.
- DEnsure the cluster is launched across multiple Availability Zones.
- EReplace Amazon EFS with multiple Amazon EBS volumes in a RAID array.
- FReplace Amazon EFS with Amazon FSx for Lustre.
How the community answered
(35 responses)- A49% (17)
- B31% (11)
- D6% (2)
- E14% (5)
Why each option
To achieve maximum performance for a large, tightly coupled HPC cluster with shared files, launch it within a single Availability Zone, select EC2 instances with Elastic Fabric Adapter (EFA), and replace Amazon EFS with Amazon FSx for Lustre for high-performance shared storage.
For tightly coupled HPC workloads, launching the cluster within a single Availability Zone minimizes network latency between instances, which is critical for achieving maximum performance for inter-node communication.
Attaching elastic network interfaces in multiples of four is not a standard or specific performance optimization for HPC; network interface configuration is generally driven by throughput requirements rather than fixed numerical multiples.
Elastic Fabric Adapter (EFA) provides high-throughput, low-latency network communication for EC2 instances, making it ideal for tightly coupled HPC applications that rely heavily on Message Passing Interface (MPI) or similar communication protocols at scale.
Spreading a tightly coupled HPC cluster across multiple Availability Zones introduces higher inter-instance network latency, which degrades performance for workloads that are sensitive to communication overhead.
Amazon EBS volumes are block storage attached to individual instances and cannot inherently provide a *shared* file system across 1,000 EC2 instances for 'a large number of shared files'; this would require a fundamental re-architecture of the storage model.
Amazon FSx for Lustre is a high-performance file system optimized for compute-intensive workloads like HPC, offering significantly higher throughput and lower latency than Amazon EFS, which can become a bottleneck for very large clusters with intense I/O demands.
Concept tested: HPC networking, shared file systems, performance optimization, EC2 instance types
Source: https://aws.amazon.com/hpc/efa/
Community Discussion
No community discussion yet for this question.