TE
科技回声
首页24小时热榜最新最佳问答展示工作
GitHubTwitter
首页

科技回声

基于 Next.js 构建的科技新闻平台,提供全球科技新闻和讨论内容。

GitHubTwitter

首页

首页最新最佳问答展示工作

资源链接

HackerNews API原版 HackerNewsNext.js

© 2025 科技回声. 版权所有。

A performance test of SQS

12 点作者 sorenso超过 10 年前

4 条评论

jdub超过 10 年前
There&#x27;s some confusion in this post about the testing methodology vs. the implementation of SQS itself.<p>SQS itself may well be implemented on EC2 instances with auto-scaling (though I doubt it), but that&#x27;s irrelevant to the test harness, which needs to scale out the number of nodes pounding on SQS.<p>The important bit is that SQS doesn&#x27;t exhibit any of the scaling bumpiness of ASGs. It&#x27;s a region-wide service, which you&#x27;d be very lucky to break on your own.
评论 #8708779 未加载
euphemize超过 10 年前
In our experience of ELB&#x2F;SQS, AWS has done a good job on these services. A few things we noted:<p>- ELB takes about ~15 minutes to scale out completely when you hit traffic spikes.<p>- SQS is simple to use, rather cost-effective and quite reliable. It will add a bit of latency, but as the author notes, this can&#x27;t replace Kinesis.<p>- The redrive policy on SQS is really nice to catch corner cases.
评论 #8708784 未加载
mbell超过 10 年前
&gt; It seems to have a problem with handling more than 2.3K message insert&#x2F;sec.<p>We&#x27;ve written to SQS at rates several times this using only 3 EC2 nodes without issue.<p>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.
评论 #8708788 未加载
noso超过 10 年前
Really good write and useful for a project I am working on!
评论 #8708791 未加载