From a7a37062f63532e189f385d075a20c51f62a8633 Mon Sep 17 00:00:00 2001 From: Gert Leenders Date: Thu, 9 Aug 2018 14:25:17 +0200 Subject: [PATCH] Changed to formula for concurrent invokations Just a detail but it could possible confuse people otherwise... --- doc_source/scaling.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/doc_source/scaling.md b/doc_source/scaling.md index e0f55d19..b0c038a2 100644 --- a/doc_source/scaling.md +++ b/doc_source/scaling.md @@ -3,7 +3,7 @@ Concurrent executions refers to the number of executions of your function code that are happening at any given time\. You can estimate the concurrent execution count, but the concurrent execution count will differ depending on whether or not your Lambda function is processing events from a poll\-based event source\. If you create a Lambda function to process events from event sources that aren't poll\-based \(for example, Lambda can process every event from other sources, like Amazon S3 or API Gateway\), each published event is a unit of work, in parallel, up to your account limits\. Therefore, the number of events \(or requests\) these event sources publish influences the concurrency\. You can use the this formula to estimate your concurrent Lambda function invocations: ``` -events (or requests) per second * function duration +events (or requests) per second * function duration (in seconds) ``` For example, consider a Lambda function that processes Amazon S3 events\. Suppose that the Lambda function takes on average three seconds and Amazon S3 publishes 10 events per second\. Then, you will have 30 concurrent executions of your Lambda function\. @@ -43,4 +43,4 @@ See [AWS Lambda Limits](limits.md) for Immediate Concurrency Increase limits for Because Lambda depends on Amazon EC2 to provide Elastic Network Interfaces for VPC\-enabled Lambda functions, these functions are also subject to Amazon EC2's rate limits as they scale\. If your Amazon EC2 rate limits prevent VPC\-enabled functions from adding **500 concurrent invocations per minute**, please request a limit increase by following the instructions on the [AWS Lambda Limits](limits.md) page\. Beyond this rate \(i\.e\. for applications taking advantage of the full Immediate concurrency increase\), your application should handle Amazon EC2 throttling \(502 EC2ThrottledException\) through client\-side retry and backoff\. For more details, see [Error Retries and Exponential Backoff in AWS](http://docs.aws.amazon.com/general/latest/gr/api-retries.html)\. -To learn how to view and manage the concurrent executions for your function, see [Managing Concurrency](concurrent-executions.md) \ No newline at end of file +To learn how to view and manage the concurrent executions for your function, see [Managing Concurrency](concurrent-executions.md)