Lambda billing duration for normal traffic

Question

While I made single request at a time, lambda duration is 500 ms or less. But when I set 50 users concurrency and 10 users started per sec (spawn rate) in LOCUST, lambda duration would be 15000 ms. My Mongodb free tier is 500 connection limit and limit is not reached anytime. When I give traffic , billing duration would be more but 500 ms for very small traffic. Is it lambda side problem or Mongodb side problem?

**I have made load testing on single api.

Brettski-AWS · Accepted Answer

Is it possible that as your concurrency goes up the MongoDB is taking longer to respond? I would instrument your Lambda function - you can do this by using log statements inside the function and measuring the time between them; or you can use something like [X-Ray](https://aws.amazon.com/xray/).

Lambda billing duration for normal traffic

Relevant content