The concurrency limit for the DB Proxy lambda function increased from 15 to 50 #1081
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Related Issue
For the DB Proxy Lambda function, which is handling everything database related (more information in this blog post), we had the default Lambda function concurrency limit set to 15. Basically, this means that we can have 15 concurrent invocations of the DB Proxy Lambda function, which, as it turned out, is not hard to reach, even in local development. To prevent this, we decided to increase this value to 50, which will significantly help in preventing the concurrency limit to be reached again.
Note that the
concurrencyLimit
parameter can still be found inapi/resources.js
andapps/resources.js
files. So, if further adjustments are needed, they can be made there.How Has This Been Tested?
Manual testing.
Screenshots (if relevant):
N/A