Company B provides an online image recognition service and utilizes SOS to decouple
system components for scalability The SQS consumers poll the imaging queue as often as
possible to keep end-to-end throughput as high as possible. However, Company B is
realizing that polling in tight loops is burning CPU cycles and increasing costs with empty
responses. How can Company B reduce the number of empty responses?
A.
Set the imaging queue visibility Timeout attribute to 20 seconds
B.
Set the DelaySeconds parameter of a message to 20 seconds
C.
Set the Imaging queue ReceiveMessageWaitTimeSeconds attribute to 20 seconds
D.
Set the imaging queue MessageRetentionPeriod attribute to 20 seconds
C
0
0
C
0
0
What that is is to enable ‘long polling’ on the que
0
0
c
0
0
C ReceiveMessageWaitTimeSeconds is API option for Long Polling on the portal
http://docs.aws.amazon.com/AWSSimpleQueueService/latest/SQSDeveloperGuide/sqs-long-polling.html
0
0
Excellent! Thanks
0
0
C
The solution is to increase the long polling timeout (Maximum 20 seconds)
http://docs.aws.amazon.com/AWSSimpleQueueService/latest/SQSDeveloperGuide/sqs-long-polling.html
The following example shows another way to enable long polling. Here, the ReceiveMessageWaitTimeSeconds attribute for the SetQueueAttributes action is set to 20 seconds.
0
0
Sorry that the solution should be “enable the long polling”
0
0
C
0
0
C
0
0