News for hackers. Stuff that matters.
Re:Feeding data to 1000 CPUs – comparison of S3, Google, Azu... by hrez on Tuesday January 05, 2016 @07:04PM (#10847227)
What missing from description is network setup. Is it ec2 classic, VPC? Is ec2 getting to s3 through IG? Hopefully not through NAT. There is also VPC endpoint to s3. Which all may have different performance profiles especially with multiple instances.
Re:Feeding data to 1000 CPUs – comparison of S3, Google, Azu... by zbjornson on Tuesday January 05, 2016 @08:05PM (#10847585)
Network was VPC. The EC2 instance had an IG attached, yes, but I'm not sure if you're asking if an internal vs. external URL for S3 was used? Are you saying there's a better endpoint than s3-<region>.amazonaws.com for S3 requests from EC2?
Re:Feeding data to 1000 CPUs – comparison of S3, Google, Azu... by hrez on Tuesday January 05, 2016 @08:46PM (#10847835)
I meant http://docs.aws.amazon.com/AmazonVPC/latest/UserGuide/vpc-en...

It's a private connection to AWS services including S3. You'd use the same URL as it's a routing basically. No idea if VPC endpoints would be better than IG though. P.S. Just tested and I get about half of the latency on VPC endpoint.

Re:Feeding data to 1000 CPUs – comparison of S3, Google, Azu... by zbjornson on Tuesday January 05, 2016 @08:57PM (#10847872)
Neat, did not know about that. Will add it to my follow-up benchmarks. Thanks for all the comments. :)