A PDF-merge Lambda for council packets is CPU-bound and slow at 128 MB. What should the developer remember when tuning memory?
Select an answer to reveal the explanation.
Short Explanation
On Lambda, memory is the volume knob that also turns up CPU—more RAM, more compute horsepower for that PDF mash-up. Don't guess 128 MB forever or assume memory and CPU are strangers; profile, raise memory, and measure duration and cost together.
Full Explanation
Lambda allocates CPU power proportional to configured memory, so increasing memory can reduce duration for CPU-bound workloads such as PDF merges. Memory and CPU are not independent knobs. Staying arbitrarily at 128 MB or relying only on reserved concurrency does not address insufficient CPU for the workload; sizing should follow profiling data.