Spring lambda having async mechanism with preserver-concurrency enabled still taking ~2.5 seconds for first request

[siddiquebagwan-gslab]

• Framework version: 1.4 (aws-serverless-java-container-spring)
• Implementations: Spring

Scenario

Stub Spring lambda having preserve concurrency and async initialisation in constructor as per code example given in README https://github.com/awslabs/aws-serverless-java-container/wiki/Quick-start---Spring in section Asynchronous initialisation

Expected behaviour

First invocation should take milli seconds time. As we just have stub api which is returning hard-coded simple POJO having 4 simple string attributes and preserve-concurrency is enabled

Actual behaviour

First invocation is taking ~2.5 seconds and subsequent is getting served in milliseconds ~600 milliseconds

Steps to reproduce

Verify above behaviour with sample app

Full log output

[sapessi]

This is because Spring loads components when they are actually needed. I'd avoid using the async initializer with provisioned concurrency. This is a good question, I'll leave the issue open and investigate with the Lambda team if there's anything we can do to make it simpler.

[siddiquebagwan-gslab]

Hi,
Any update ?

[sapessi]

Hi @Mohd-gslab, yes. This is probably related to #287. Good news is that we have a fix for it in the v1.5 branch of this repo. Any chance you could test with the version from the branch?

[siddiquebagwan-gslab]

Thanks I will test and let you know by Monday EOD

On Fri, 3 Apr 2020 at 3:47 AM, Stefano Buliani ***@***.***> wrote: Hi @Mohd-gslab <https://github.com/Mohd-gslab>, yes. This is probably related to #287 <#287>. Good news is that we have a fix for it in the v1.5 branch of this repo. Any chance you could test with the version from the branch? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#322 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AHG5YWLNSWTSDMMXXL3A4XLRKUFIJANCNFSM4KULHLPQ> .

-- Sent from my iPhone, pardon typo

…

-- Confidentiality Notice and Disclaimer: This email (including any attachments) contains information that may be confidential, privileged and/or copyrighted. If you are not the intended recipient, please notify the sender immediately and destroy this email. Any unauthorized use of the contents of this email in any manner whatsoever, is strictly prohibited. If improper activity is suspected, all available information may be used by the sender for possible disciplinary action, prosecution, civil claim or any remedy or lawful purpose. Email transmission cannot be guaranteed to be secure or error-free, as information could be intercepted, lost, arrive late, or contain viruses. The sender is not liable whatsoever for damage resulting from the opening of this message and/or the use of the information contained in this message and/or attachments. Expressions in this email cannot be treated as opined by the sender company management – they are solely expressed by the sender unless authorized.

[vs-cpalacios]

Hi. I have the same problem, even with v1.5. @Mohd-gslab Did you find out how to solve it? Thanks in advance

[siddiquebagwan-gslab]

No, I didn’t got solution and I shifted to python (AWS CHALICE)

On Sun, 5 Jul 2020 at 5:52 AM, vs-cpalacios ***@***.***> wrote: Hi. I have the same problem, even with v1.5. @Mohd-gslab <https://github.com/Mohd-gslab> Did you find out how to solve it? Thanks in advance — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#322 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AHG5YWJKD67OKC6IWLRTX53RZ7BV3ANCNFSM4KULHLPQ> .

-- Sent from my iPhone, pardon typo

…

-- Confidentiality Notice and Disclaimer: This email (including any attachments) contains information that may be confidential, privileged and/or copyrighted. If you are not the intended recipient, please notify the sender immediately and destroy this email. Any unauthorized use of the contents of this email in any manner whatsoever, is strictly prohibited. If improper activity is suspected, all available information may be used by the sender for possible disciplinary action, prosecution, civil claim or any remedy or lawful purpose. Email transmission cannot be guaranteed to be secure or error-free, as information could be intercepted, lost, arrive late, or contain viruses. The sender is not liable whatsoever for damage resulting from the opening of this message and/or the use of the information contained in this message and/or attachments. Expressions in this email cannot be treated as opined by the sender company management – they are solely expressed by the sender unless authorized.

[sapessi]

@vs-cpalacios can you share the logs you see for the cold start + first invocation?