-
Notifications
You must be signed in to change notification settings - Fork 232
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SnapStart Support #380
Comments
Hi @softprops, Could you give more detail regarding what you would like to see added? |
I believe SnapStart is only supported for java11 managed runtime |
That’s my understanding as well based on what I’ve read so far. I’ve recently upgraded to java 17 (thanks @msailes for the awesome java 17 layer project). I’m loving java 17 and would like to not have to give that up and have to down grade just to get this lambda snapstart benefit. the docs mentioned it’s implemented in the runtime so I’m presuming that means in the client that handles the lambda runtime api requests. Does the official java11 lambda runtime use the same runtime api client as the one in this project? If so I may get this for free and I can close out this issue. |
Did I misread something, or there's no answer to the original question...? @softprops @msailes or is this addressed somewhere else? |
There is no change required in this project for SnapStart. |
Awesome! to clarify, should I expect snapstart should work out of the box for those using a provided runtime using this projects client as a handler executor and corretto as the jvm? |
SnapStart is only available for Java 11. |
@msailes Is there any timeline for when the official Java 17 runtime with the SnapStart support might be available |
We are continuing to work on Java 17 support, but don't currently have a timeline we can share. |
https://aws.amazon.com/blogs/compute/reducing-java-cold-starts-on-aws-lambda-functions-with-snapstart/
Is it possible to add this new lambda feature to the lambda runtime api client?
The text was updated successfully, but these errors were encountered: