AWS drops bandwidth pricing
61–70 of 96 posts
Re: AWS drops bandwidth pricing
#62Making all in-bound traffic free is a super-aggressive (and much appreciated) move. As blhack pointed out Voxel's per-GB rate[1] before AWS dropped was extremely competitive, but they charge for in and out-bound data. AWS, after the 1st of July will only charge $0.12 for out-bound data and $0.00 for inbound data, effectively making it something like $0.06/GB compared to Voxel (I'm hand-waving this a bit to make a poi…
for 99% of websites...$0.12/gb OUT and 0.0/gb IN will not effectively make this $0.06/gb.
Re: AWS drops bandwidth pricing
#63This is probably a move in response to Windows Azure dropping its inbound data transfer rates to zero last week. When I was back in Windows Azure, we would often see AWS try to do a price-match whenever we changed prices drastically.
Re: AWS drops bandwidth pricing
#64For another comparison, voxel.net (which serves imgur): http://www.voxel.net/pricing $0.10/GB up to 40TB $0.07/GB up to 500TB $0.05/GB >500TB This looks like the cheapest "real" CDN I've seen. Awesome :) Not that I need it [yet], but here's to hoping :)
Re: AWS drops bandwidth pricing
#65I was going to look into deployment scripts for App Engine, but Amazon makes it more compelling to use AWS.
Re: AWS drops bandwidth pricing
#66Making all in-bound traffic free is a super-aggressive (and much appreciated) move. As blhack pointed out Voxel's per-GB rate[1] before AWS dropped was extremely competitive, but they charge for in and out-bound data. AWS, after the 1st of July will only charge $0.12 for out-bound data and $0.00 for inbound data, effectively making it something like $0.06/GB compared to Voxel (I'm hand-waving this a bit to make a poi…
for 99% of websites...$0.12/gb OUT and 0.0/gb IN will not effectively make this $0.06/gb.
Re: AWS drops bandwidth pricing
#67Earlier quoted context omitted.
for 99% of websites...$0.12/gb OUT and 0.0/gb IN will not effectively make this $0.06/gb.
Can you elaborate on this? Not disputing your point, but it would be nice if someone could jump in with some real world numbers or a rule of thumb.
Here's a somewhat old article that captures the rule.
http://www.guardian.co.uk/technology/2006/jul/20/guardianwee...
Re: AWS drops bandwidth pricing
#68Earlier quoted context omitted.
Instances are already IO bound/capped. For example, if you start up a micro instance, you'll only be able to download at like 200kbps or something. So I'd assume the connection speed is linked to the size of the instance, and the bandwidth cost is integrated into that cost somewhat.
I don't think this is accurate. I have seen download speeds of around 6/8MBps on windows micro instances. The lowest I got was around 3MBps. But I only tried with downloads of around 30MB files at the maximum.
Re: AWS drops bandwidth pricing
#69Earlier quoted context omitted.
Instances are already IO bound/capped. For example, if you start up a micro instance, you'll only be able to download at like 200kbps or something. So I'd assume the connection speed is linked to the size of the instance, and the bandwidth cost is integrated into that cost somewhat.
I don't think this is accurate. I have seen download speeds of around 6/8MBps on windows micro instances. The lowest I got was around 3MBps. But I only tried with downloads of around 30MB files at the maximum.
wget -O /dev/null http://cachefly.cachefly.net/100mb.test
gives me about 30 MBytes/s from a micro instance in EU-WestRe: AWS drops bandwidth pricing
#70Earlier quoted context omitted.
I don't think this is accurate. I have seen download speeds of around 6/8MBps on windows micro instances. The lowest I got was around 3MBps. But I only tried with downloads of around 30MB files at the maximum.
The io is burstable. Try doing a sustained large download and you will see the speed throttle down