Issue link: https://read.uberflip.com/i/1187300
Amazon Web Services – HPC Lens AWS Well-Architected Framework Page 38 Review When architecting solutions, there is a finite set of options from which you can choose. However, over time new technologies and approaches become available that can improve the performance of your architecture. Monitoring After you have implemented your architecture, you will need to monitor its performance so that you can fine-tune it for maximum performance. Monitoring metrics should be used to gain insight into resource performance and raise alarms when thresholds are breached. The alarm can trigger automated action to work around any poorly performing components. In addition to the monitoring considerations outlined in the AWS Well- Architected Framework whitepaper, many HPC users find detailed Amazon EC2 monitoring useful when gauging application performance. Detailed monitoring shortens the monitoring interval from five minutes to one minute for your instance metrics. Detailed monitoring can be enabled through the AWS Management Console, CLI, or API. Trade-offs When you architect solutions, think about trade-offs so you can select an optimal approach. Depending on your situation you could trade consistency, durability, and space versus time or latency to deliver higher performance. Cost Optimization Pillar The cost optimization pillar includes the continual process of refinement and improvement of an HPC system over its entire lifecycle. From the initial design of your first proof of concept to the ongoing operation of production workloads, adopting the practices in this paper will enable you to build and operate cost- aware systems that achieve business outcomes and minimize costs, thus allowing your business to maximize its return on investment. Design Principles For HPC in the cloud you can follow a number of principles to achieve cost optimization: • Adopt a consumption model: Pay only for the computing resources that you consume. HPC workloads ebb and flow, providing the