The aws_sqs source has support for client concurrency, running more than one polling client thread at once. This defaults to one client per CPU currently. However, those threads will frequently be idle, resulting in excess unnecessary polling, and also cannot be scaled beyond the configured concurrency. This source could adapt the auto-concurrency idea from gcp_pubsub (#13240) and scale its connections dynamically as there is discovered need for higher loading. This would allow us to scale our use of the SQS API to current conditions rather than requiring configuration for the worst case loading.
The
aws_sqs
source has support for client concurrency, running more than one polling client thread at once. This defaults to one client per CPU currently. However, those threads will frequently be idle, resulting in excess unnecessary polling, and also cannot be scaled beyond the configured concurrency. This source could adapt the auto-concurrency idea fromgcp_pubsub
(#13240) and scale its connections dynamically as there is discovered need for higher loading. This would allow us to scale our use of the SQS API to current conditions rather than requiring configuration for the worst case loading.