Tips to Optimize Your AWS Lambda Performance

If you actually have a consistent&#x2F;constant load then you don&#x27;t need to pay for Provisioned Concurrency to prevent cold starts since you technically will have the equivalent with your actual usage.<p>Also, if you&#x27;re using Lambda to ingest data consider using one lambda as a dispatcher to SQS and another hanging off that SQS queue for processing. That allows you to control concurrency better since you can set the batch size + concurrency on the SQS trigger.<p>By doing the above makes your critical path super-fast, because you&#x27;re doing no processing. That works great if the incoming data needs no response from the back-end.

&quot;You should set your PC value equal to your peak TPS divided by the execution time. For example, if you have a peak of 50 TPS and your execution time is half a second, the most effective PC value would be 25.&quot;<p>This confused me. Wouldn&#x27;t 50 &#x2F; 0.5 be 100?

I still don&#x27;t understand why anyone would use lambdas - except if you 1) trust Amazon blindly, and 2) have no understanding whatsoever of how a server works, and therefore absolutely unable to set one up (even as a AWS instance, LOL).<p>From my experience, they are clumsy, complex to set up, to manage, you can&#x27;t easily have CI&#x2F;CD (I still don&#x27;t know how you get the code of a lambda from and to git ?!?!), etc, etc...<p>Is it just me ? Am I alone ?<p>:)