You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Even just using TieredStopAtLevel=1 my team has seen the cold start times cut in half for many of our Lambda functions. I do think this is something that has more of an affect when you have more initialization code though, so it might not provide as much benefit in this package, since the code in the lambda is minimal. It might be worth a try, and would be a good data point.
I have not measured the results for the combination yet, but Tiered Compilation can also be combined with SnapStart.
The text was updated successfully, but these errors were encountered:
The other article explains how to do the same thing with a layer, which is probably overkill for this project. A simple environment variable should be much easier to add.
I've seen good improvements for Lambda functions written in Java using tiered compilation, as described in this article:
https://aws.amazon.com/blogs/compute/increasing-performance-of-java-aws-lambda-functions-using-tiered-compilation/
Even just using TieredStopAtLevel=1 my team has seen the cold start times cut in half for many of our Lambda functions. I do think this is something that has more of an affect when you have more initialization code though, so it might not provide as much benefit in this package, since the code in the lambda is minimal. It might be worth a try, and would be a good data point.
I have not measured the results for the combination yet, but Tiered Compilation can also be combined with SnapStart.
The text was updated successfully, but these errors were encountered: