Instiq
Chapter 5 · Troubleshooting and Optimization·v2.1.0·Updated 6/28/2026·~8 min

What's changed: In-scope service coverage (axis B): added Athena/OpenSearch Service large-scale log-analysis definitions, roles, and selection criteria to s1 (CloudWatch).

5.3Optimizing Performance and Cost

Key points

Understand optimization: caching (ElastiCache/DAX/CloudFront), Lambda tuning (memory/concurrency/cold-start mitigation), and efficient data access (Query, retries with exponential backoff, pagination).

Once you measure and find issues, make it faster and cheaper. Caching, compute tuning, and efficient data access are the staple levers.

5.3.1Optimization levers

Diagram of three levers: caching (ElastiCache/DAX, CloudFront at edge; cut latency and load), tuning compute (Lambda memory/timeout, right-size, concurrency, avoid cold starts), and efficient data access (Query not Scan, retries with backoff, pagination).
Levers for performance/cost optimization
  • Caching: ElastiCache/DAX (in front of DynamoDB) or CloudFront (edge) to cut latency and DB load.
  • Lambda tuning: adjust memory for CPU; use provisioned concurrency to mitigate cold starts.
  • Efficient data access: Query not Scan, retries with exponential backoff for throttling, pagination for large results.
Exam point

Common on DVA: speed up reads = caching (CloudFront/ElastiCache/DAX), mitigate cold starts = provisioned concurrency, throttling (429 / ProvisionedThroughputExceeded) = retry with exponential backoff, avoid Scan, use Query.

Continue reading — free sign-up

You're reading the free preview. Sign up free to read this section in full, plus every chapter (including 4+) and all questions.