Provisioned Concurrency is not working as expected #9341
Replies: 7 comments 1 reply
-
Hello @mydeen1989. Please follow the template that is present when you create a new issue. Additionally, do you have the ability to upgrade to the latest version of the Framework? In |
Beta Was this translation helpful? Give feedback.
-
@pgrzesik Thanks for your quick reply. Let me try to upgrade the serverless |
Beta Was this translation helpful? Give feedback.
-
@pgrzesik . Serverless upgraded to latest version and redeployed in aws Framework Core: 2.35.0 (local) Still my response time is higher. I couldn't see any provisioned concurrency metrics in Invocations widget. |
Beta Was this translation helpful? Give feedback.
-
@mydeen1989 Please follow the issue template that is visible when you create a new issue, ideally please provide minimal reproducible example of your issue. |
Beta Was this translation helpful? Give feedback.
-
Q1: Describe the issue Provisioned Concurrency is not working as expected . I have added provisionedConcurrency : 3 in serverless.yml to fix the cold start issue. But still I am getting the higher response time. Q2: Provide FULL content of serverless.yml
Q3: Q4 : serverless version Framework Core: 2.35.0 (local) |
Beta Was this translation helpful? Give feedback.
-
Thanks for providing additional details @mydeen1989. I've tried to reproduce and I see that both generated CloudFormation file as well as deployed configuration is correct for streams with provisioned concurrency enabled. As it seems to be more of a general support question instead of bug report in Serverless Framework, I'm moving it to discussion sections (this tracker is aimed at bugs/improvement proposals). |
Beta Was this translation helpful? Give feedback.
-
Hi,
I am new user to serverless framework. My lambda is throwing higher response time. When I see the documentation it can fix by provisionedConcurrency. I tried to add the same in my serverless.yml but still my issue is not resolved.
Serverless version
Framework Core: 1.83.3 (local)
Plugin: 3.8.4
SDK: 2.3.2
Components: 2.34.9
Added provisionedConcurrency: 3 and versionFunctions: false in serveless.yml
able to see the same in aws console.
I have added the below code to verify the cold start fix
var coldStart = true;
console.log("This line of code exists outside the handler, and only executes on a cold start >>>> in Connect lambda");
exports.handler = async event => {
if (coldStart) {
console.log("First time the handler was called since this function was deployed in this container");
}
coldStart = false;
I can see this log "First time the handler was called since this function was deployed in this container" whenever the lambda function newly invoked.
I have noticed the below logs after lambda deployed
There is no metrics in provisionedConcurrency Invocations. Still my response time higher after I have added provisionedConcurrency: 3 . Could you please help me to resolve this.
Beta Was this translation helpful? Give feedback.
All reactions