PERF 13. How do you select the appropriate proximity and caching solutions for your system?
Physical distance, network distance, or long running requests can introduce system delays. Unaddressed latency can tie up system resources for longer than required, and introduce both internal and external performance degradation. To reduce latency, consider the end-to-end performance of your entire system from the end-user’s perspective, and look for opportunities to adjust the physical proximity of your resources or cache solutions.
Best practices:
 Policy/Reference Architecture Select instance type and size based on predicted resource need based on an internal governance standard.
 Cost/Budget Selecting instance type and size based on predicted resource need based on internal cost controls.
 Benchmarking Load test a known workload on AWS and use that to estimate the best selection; testing a known performance benchmark vs. a known workload.
 Guidance from AWS or from an APN Partner Select a proximity and caching solution based on best practice advice.
 Load Test Deploy the latest version of your system on AWS using different instance types and sizes, use monitoring to capture performance metrics, and then make a selection based on a calculation of performance/cost.