Examples of using Concurrent execution in English and their translations into Spanish
{-}
-
Colloquial
-
Official
Account Level Concurrent Execution Limit.
Retrospect Desktop does not support multiple concurrent executions.
Function Level Concurrent Execution Limit.
Concurrent executions greater than 25 are automatically added to an execution queue.
To request a limit increase for concurrent executions.
The maximum of concurrent executions you want reserved for the function.
AWS Lambda dynamically scales capacity in response to increased traffic,subject to your account's concurrent execution limit.
Cloud Functions limits concurrent executions to 1 per instance.
Concurrent executions to multiple tape drives requires Retrospect's Advanced Tape Support addon.
You can optionally set the concurrent execution limit for a function.
Concurrent executions refers to the number of executions of your function code that are happening at any given time.
AWS Lambda currently supports 1000 concurrent executions per AWS account per region.
By setting a concurrent execution limit on a function, you are reserving the specified concurrent execution value for that function.
AWS Lambda will dynamically scale capacity inresponse to increased traffic, subject to your account's Account Level Concurrent Execution Limit.
Multitasking for concurrent execution of up to eight application programs.
Improved data transfer for concurrent execution, including a minimum delay mode.
If you set the concurrent execution limit for a function, the value is deducted from the unreserved concurrency pool.
Being able to replicate the concurrent execution of transactions taking the isolation level into account.
You can set the concurrent execution limit for a function to match the subnet size limits you have.
To assist with this, Lambda provides a concurrent execution limit control at both the account level and the function level.
You can set the concurrent execution limit for a function to align with the values of its downstream resources support.
ConcurrentExecutions: This shows you the concurrent executions at an account level, and for any function with a custom concurrency limit.
The maximum number of concurrent executions of an on-demand pipeline can be configured using the slot maxActiveInstances in the Default object.
Measures the sum of concurrent executions for a given function at a given point in time.
To understand your concurrent execution usage, AWS Lambda provides the following metrics.
By default, the concurrent execution limit is enforced against the sum of the concurrent executions of all functions.
For example, if your account's concurrent execution limit is 1000 and you have 10 functions, you can specify a limit on one function at 200 and another function at 100.
The default behavior means a surge of concurrent executions in one function prevents the function you have isolated with an execution limit from getting throttled.
AWS may automatically raise the concurrent execution limit on your behalf to enable your function to match the incoming event rate, as in the case of triggering the function from an Amazon S3 bucket.