Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix(forwarder): cap number of concurrency SQS tasks #306

Merged
merged 1 commit into from
Jun 18, 2024

Conversation

jta
Copy link
Contributor

@jta jta commented Jun 14, 2024

The forwarder function processes SQS tasks concurrently. By default this value was previously unbounded, which would cause significant delay when redriving a Dead Letter Queue.

This commit changes the default to be set to the runtime number of CPUs, which allows the behaviour to scale with the amount of memory allocated to the lambda function.

@jta jta force-pushed the joao/cap-max-concurrency branch 2 times, most recently from 2e9e93d to 7bc83ea Compare June 14, 2024 18:46
The forwarder function processes SQS tasks concurrently. By default this
value was previously unbounded, which would cause significant delay when
redriving a Dead Letter Queue.

This commit changes the default to be set to the runtime number of CPUs,
which allows the behaviour to scale with the amount of memory allocated
to the lambda function.
@jta jta force-pushed the joao/cap-max-concurrency branch from 7bc83ea to a1d4e04 Compare June 18, 2024 17:24
@jta jta marked this pull request as ready for review June 18, 2024 19:28
@jta jta merged commit 421ccbc into main Jun 18, 2024
16 checks passed
@jta jta deleted the joao/cap-max-concurrency branch June 18, 2024 20:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants