- 最新
- 最多得票
- 最多評論
Concurrency equals approximately number of invocations per second * duration of the function. For example, if you invoke the function 1000 times / sec, and it takes the function 1 second to run, the concurrency will be ~1000. However, if the function takes 100ms to run, your concurrency will be ~100.
If you want to test your function at higher concurrency you either need to increase the invocation rate or extend the function duration.
It's possible that the Total concurrent executions you see on the dashboard is limited by your AWS account's overall concurrency limit, which might be set to 20. Even though you've set the reserved concurrency for one function to 200 and the account concurrency to 300, you won't be able to exceed the overall limit.
To check your account's overall concurrency limit, you can go to the "Concurrency" tab in the Lambda console and look for the "Account concurrency" section. If it's set to 20, you can request an increase in your account concurrency limit by following the instructions provided in the console.
Another possibility is that your function is experiencing throttling due to exceeding its own concurrency limit, which might be set to a lower value than the reserved concurrency you've configured. You can check the function's concurrency configuration by going to the function's "Concurrency" tab in the Lambda console.
If none of the above explanations seem to apply, you might want to look at your function's CloudWatch logs to see if there are any errors or messages related to concurrency.
相關內容
- 已提問 1 年前
- AWS 官方已更新 1 年前
my function will take about 60s. I send about 100 request in one seconds. but only 20 concurrency