chore(ods-etl): FTRS-3588 Adjust batch size and concurrency#1011
Open
chore(ods-etl): FTRS-3588 Adjust batch size and concurrency#1011
Conversation
Contributor
There was a problem hiding this comment.
Pull request overview
This PR adjusts the SQS → Lambda event source mapping tuning for the ETL ODS pipeline to change batching and concurrency behavior for the transformer and consumer Lambdas.
Changes:
- Reduce SQS event source
batch_sizefrom 10 to 5 for both transformer and consumer triggers. - Increase
scaling_config.maximum_concurrencyfrom 5 to 15 for both triggers. - Reduce
maximum_batching_window_in_secondsfrom 5 to 2 for both triggers.
You can also share your feedback on Copilot code review. Take the survey.
c0c492c to
b945736
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description
Context
Sensitive Information Declaration
To ensure the utmost confidentiality and protect your and others privacy, we kindly ask you to NOT including PII (Personal Identifiable Information) / PID (Personal Identifiable Data) or any other sensitive data in this PR (Pull Request) and the codebase changes. We will remove any PR that do contain any sensitive information. We really appreciate your cooperation in this matter.