EC2 nodes in an HPC cluster exchange a large amount of traffic.
Place nodes close together within one Availability Zone to reduce network latency.
Which placement is most appropriate?
Use a Cluster Placement Group when close placement and high-bandwidth, low-latency communication are required.
Detailed explanation
A cluster group places instances close together in one Availability Zone for low latency and high bandwidth.
A cluster group places instances close together in one Availability Zone for low latency and high bandwidth.
S3 is not a placement target for compute instances.
S3 is not a placement target for compute instances.
DNS routing does not control the physical placement of EC2 instances.
DNS routing does not control the physical placement of EC2 instances.
Spread groups target fault isolation rather than close, low-latency placement.
Spread groups target fault isolation rather than close, low-latency placement.
Check official documentation
Compare the following points with the official documentation.
EC2 placement groupsの公式説明を確認する。
What to confirm
ClusterとSpreadの配置目的を性能要件から区別できる。
Key points
- Cluster Placement Group
- Low latency
- HPC
Notes
- Environment: AWS公式EC2ドキュメントの確認
- Confirm current AWS service behavior in the official documentation.
Foundation review
Placement objective
Cluster placement favors network performance, while spread placement favors infrastructure isolation.
Availability Zone
An isolated location within a Region that forms the scope of a cluster placement group.