PERF08-BP01 Understand the areas where performance is most critical - AWS Well-Architected Framework (2023-04-10)

PERF08-BP01 Understand the areas where performance is most critical

Understand and identify areas where increasing the performance of your workload will have a positive impact on efficiency or customer experience. For example, a website that has a large amount of customer interaction can benefit from using edge services to move content delivery closer to customers.

Desired outcome: Increase performance efficiency by understanding your architecture, traffic patterns, and data access patterns, and identify your latency and processing times. Identify the potential bottlenecks that might affect the customer experience as the workload grows. When you identify those areas, look at which solution you could deploy to remove those performance concerns.

Common anti-patterns:

  • You assume that standard compute metrics such as CPUUtilization or memory pressure are enough to catch performance issues.

  • You only use the default metrics recorded by your selected monitoring software.

  • You only review metrics when there is an issue.

Benefits of establishing this best practice: Understanding critical areas of performance helps workload owners monitor KPIs and prioritize high-impact improvements.

Level of risk exposed if this best practice is not established: High

Implementation guidance

Set up end-to-end tracing to identify traffic patterns, latency, and critical performance areas. Monitor your data access patterns for slow queries or poorly fragmented and partitioned data. Identify the constrained areas of the workload using load testing or monitoring.

Implementation steps

  1. Set up end-to-end monitoring to capture all workload components and metrics.

  2. Perform tests to generate metrics, identify traffic patterns, bottlenecks, and critical performance areas.

    • Set up CloudWatch Synthetic Canaries to mimic browser-based user activities programmatically using cron jobs or rate expressions to generate consistent metrics over time.

    • Use the AWS Distributed Load Testing solution to generate peak traffic or test the workload at the expected growth rate.

  3. Evaluate the metrics and telemetry to identify your critical performance areas. Review these areas with your team to discuss monitoring and solutions to avoid bottlenecks.

  4. Experiment with performance improvements and measure those changes with data.

Level of effort for the implementation plan: To establish this best practice, you must review your end-to-end metrics and be aware of your current workload performance. This is a moderate level of effort to set up end to end monitoring and identify your critical performance areas.

Resources

Related documents:

Related videos:

Related examples: