Live data from Hacker News

AWS drops bandwidth pricing

aws.amazon.com

61–70 of 96 posts

Re: AWS drops bandwidth pricing

#62
post #54
post #35

Making 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.

[deleted]

Re: AWS drops bandwidth pricing

#63
post #45

This 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.

I know Amazon pays very little attention to competitors. However, their customers might have asked them to lower prices in response to Azure.

Re: AWS drops bandwidth pricing

#64
post #30

For 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 :)

I use CDNetworks, and at a 50TB commit I'm getting /much/ better pricing than that... I've even been quoted better pricing than that by Akamai (which people in this industry view as notoriously expensive). I might encourage you to drop the quotes around "real" and look at actually real CDNs (the kind you have to call and negotiate pricing with): they aren't as expensive as you apparently think they are.

Re: AWS drops bandwidth pricing

#66
post #54
post #35

Making 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.

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.

Re: AWS drops bandwidth pricing

#67
post #54

Earlier 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.

It's because of the ratio of reads to writes. For many applications, especially in social/content, the creation traffic is an order of magnitude or two less than the consumption traffic. So free inbound bandwidth is a bit of a rounding error.

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

#68
post #58

Earlier 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.

The io is burstable. Try doing a sustained large download and you will see the speed throttle down

Re: AWS drops bandwidth pricing

#69
post #58

Earlier 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.

This

  wget -O /dev/null http://cachefly.cachefly.net/100mb.test
gives me about 30 MBytes/s from a micro instance in EU-West

Re: AWS drops bandwidth pricing

#70
post #68
post #58

Earlier 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

No, I'm seeing a sustained 6MB/s on this US-EAST micro.
Post reply on HN