Load tests must find the smallest Lambda memory setting that still meets p95 latency for a city PDF-merge function. What is the right optimization goal?
Select an answer to reveal the explanation.
Short Explanation
Lambda memory is also CPU—so more isn't automatically 'better,' it's just pricier. Load-test until you find the smallest setting that still clears p95 for PDF merge. That's the sweet spot between citizen wait time and the city bill.
Full Explanation
Lambda memory allocation scales CPU. Cost-effective tuning uses load tests to find the lowest memory that still meets latency objectives such as p95 for PDF merge workloads. Maximum memory by default, fixed undersizing, or sizing only by /tmp do not balance SLO and cost. Minimum viable compute that meets SLOs is the optimization target.