A Java Lambda that generates rare monthly utility reports shows multi-second cold starts when the first citizen clicks after long idle periods. Idle cost is a concern for infrequent use. What is the most appropriate performance approach?

Lambda cold starts are influenced by runtime, dependency size, and initialization work. For infrequent workloads, shrink the deployment artifact and consider a lighter runtime before paying for provisioned concurrency; use provisioned concurrency when latency SLOs justify the idle cost. Setting reserved concurrency to zero throttles invokes, and dashboards alone cannot replace compute for report generation.