4 ms·
There's some confusion in this post about the testing methodology vs. the implementation of SQS itself. SQS itself may well be implemented on EC2 instances wit
by jdub 12y ago
There's some confusion in this post about the testing methodology vs. the implementation of SQS itself.
SQS itself may well be implemented on EC2 instances with auto-scaling (though I doubt it), but that's irrelevant to the test harness, which needs to scale out the number of nodes pounding on SQS.
The important bit is that SQS doesn't exhibit any of the scaling bumpiness of ASGs. It's a region-wide service, which you'd be very lucky to break on your own.
- sorenso 12y agoThanks for commenting! I'll be happy to answer any question about my implementation and testing. In this test I'm using a standard SQS service i region EU-west. My integration with SQS is done from a simple application written in Node.js. My application is put inside an autoscaling group which scales up when the load on the servers is above my threshold. At the end of the last test I was pushing messages from 18 different servers at the same time. The request rate was above 6K/sec but the insert rate into the SQS queue only managed to peak aroud 2.3K message insert/sec. I agree that this is strange. But I've also experienced strange stuff with Amazon ELB: http://litt.no/tech%20stuff/amazon-elb-latency-problems http://litt.no/tech%20stuff/amazon-elb-latency-problems Best regards, -sorenso-