Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

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


Goto facebook, or SO, or HN or youtube or almost any site...open firebug or whatever, and calculate the amount of inbound traffic to the outbound traffic (keep in mind that this is reverse for you and the host). You should notice that your outbound traffic (their inbound), which is mostly short GET headers, is like 1% of your inbound (their outbound).

Sites where you upload a lot of content, like YouTube, still have much, much more reads (outbound) than writes (inbound). Probably by an order of magnitude.

Systems like Dropbox would benefit - though they were already getting different pricing I'm sure. But this is really a tiny fraction of how most online systems work.


Latch, very fair point. I did a bit too much hand waving there, but maybe more like $0.10/GB would be more accurate.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: