Each request that invokes a Lambda is counted as one request. Usually that's a call to your functions, like the API, or the Files service to retrieve a file.

Functions are identified as all requests on a /function/ path. For example like /function/api which is the path for the default Webiny API.

When it comes to files. All requests that are on the /files/ path might hit a lambda function. We say "might" because responses from those requests have several layers of caching. They are cached on the CDN and on the user's browser. In case the request is delivered from those caches, the request won't be counted as a lambda request.

File service also has one more part, which is uploading or deleting files from the storage. When you upload a file, that will partially through a lambda function, same happens when a file is removed. Files like different image size transformations get automatically purged after 90 days that they have not been accessed. Note that the original image file is never automatically deleted.

Lastly, your usage statistics, and later performance statistic are tracked and automatically processed every 5 minutes by a lambda function. Each processing is calculated as one lambda request.

Note that if you website doesn't have traffic, the processing for the usage statistics isn't triggered at any point.

The time from when the request was received, until the time a response is delivered, or request is terminated, is counted as the run time. The run time is rounded to the nearest 100ms.
Was this article helpful?
Cancel
Thank you!