aws-lambda-power-tuning

I enjoyed reading this analysis, even if it is quite specific to a single situation. I agree with the writer's larger point that you need to do this kind of analysis for your workload, in your conditions, to draw the right conclusions. > This does lead to a caveat with analysis, however: larger Lambda’s may actual process more quickly than ones that are more right sized, potentially leading to cheaper outcomes. This is an important thing to include for compute-bound tasks (which is a suprisingly large number of tasks, at least up to some limit). There are some nice third party projects (like Lambda Power Tuning[2]) that can help find the sweet spot on price versus performance (with their own caveats, of course). > Consider using Lambda without API Gateway Yes! API Gateway can add a lot of value when you need it, but if you don't need it t

On the subject of AWS Lambda cost and time optimization: also check out AWS Lambda Power Tuning [^1] and its ecosystem of projects. It also supports 1ms billing and 10GB of RAM. [^1]: https://github.com/alexcasalboni/aws-lambda-power-tuning