28 ms·
> It seems to have a problem with handling more than 2.3K message insert/sec. We've written to SQS at rates several times this using only 3 EC2 nodes without i
by mbell 12y ago
> It seems to have a problem with handling more than 2.3K message insert/sec.
We've written to SQS at rates several times this using only 3 EC2 nodes without issue.
The only issue we have seen is occasional and sporadic latency issues reading from SQS which causes the queues to backup a bit but it generally clears within 30 minutes or so.
- sorenso 12y agoHi mbell, Thanks for commenting! What kind of application are you using with the SQS (language, purpose, usage)? It would be interesting to know for me :) This test was only running for 50 minutes, maybe this could be the issue? Best regards, -sorenso-
- mbell 12y agoWe use SQS as a buffer at the front of an analytics system. The enqueuing app is written in Java using Dropwizard and Apache Camel. Average message size is probably ~1KB.