Comments on: Real world case study in slimming down bandwidth consumption http://www.ajaxperformance.com/2007/03/08/real-world-case-study-in-slimming-down-bandwidth-consumption/ A blog by Ryan Breen of Gomez Mon, 01 Dec 2008 21:33:59 +0000 http://wordpress.org/?v=2.6.2 By: Ryan Breen http://www.ajaxperformance.com/2007/03/08/real-world-case-study-in-slimming-down-bandwidth-consumption/#comment-2752 Ryan Breen Tue, 13 Mar 2007 15:14:32 +0000 http://www.ajaxperformance.com/?p=54#comment-2752 Great info, thanks Buddy. So, there you have it. S3 gives you the best of both worlds: no bandwidth impact on your host and 6 concurrent connections to the browser. Great info, thanks Buddy.

So, there you have it. S3 gives you the best of both worlds: no bandwidth impact on your host and 6 concurrent connections to the browser.

]]> By: Buddy Brewer http://www.ajaxperformance.com/2007/03/08/real-world-case-study-in-slimming-down-bandwidth-consumption/#comment-2751 Buddy Brewer Tue, 13 Mar 2007 15:02:12 +0000 http://www.ajaxperformance.com/?p=54#comment-2751 S3 works nicely with DNS virtual hosting. For example, if you create three buckets in S3 called mydomain-static[1-3], AWS will let you refer to those buckets as mydomain-staticN.s3.amazonaws.com. Thanks to S3's REST interface, objects inside buckets can be addressed using the Request-URI path. You can also set up prettier domains like static1.mydomain.com using DNS CNAME records. See the <a href="http://docs.amazonwebservices.com/AmazonS3/2006-03-01/VirtualHosting.html" title="Virtual hosting of buckets" rel="nofollow">S3 docs</a> for more info. S3 works nicely with DNS virtual hosting. For example, if you create three buckets in S3 called mydomain-static[1-3], AWS will let you refer to those buckets as mydomain-staticN.s3.amazonaws.com. Thanks to S3’s REST interface, objects inside buckets can be addressed using the Request-URI path. You can also set up prettier domains like static1.mydomain.com using DNS CNAME records. See the S3 docs for more info.

]]> By: Ryan Breen http://www.ajaxperformance.com/2007/03/08/real-world-case-study-in-slimming-down-bandwidth-consumption/#comment-2622 Ryan Breen Sun, 11 Mar 2007 01:35:08 +0000 http://www.ajaxperformance.com/?p=54#comment-2622 wiotta, That's interesting, but in that approach you would need to proxy the connections back through S3, so you would be taking both an inbound (from S3) and outbound (to the client) bandwidth hit. I was hoping for a solution that gives the client 6 parallel connections to S3 without any bandwidth impact on us. Ryan wiotta,
That’s interesting, but in that approach you would need to proxy the connections back through S3, so you would be taking both an inbound (from S3) and outbound (to the client) bandwidth hit. I was hoping for a solution that gives the client 6 parallel connections to S3 without any bandwidth impact on us.
Ryan

]]> By: wioota http://www.ajaxperformance.com/2007/03/08/real-world-case-study-in-slimming-down-bandwidth-consumption/#comment-2619 wioota Sat, 10 Mar 2007 23:14:58 +0000 http://www.ajaxperformance.com/?p=54#comment-2619 I wonder whether you could create your own service hosted on a number of separate lighttpd instances which handles retrieval out of s3 whilst giving you the variety in host names you need to beat the connection limit. I wonder whether you could create your own service hosted on a number of separate lighttpd instances which handles retrieval out of s3 whilst giving you the variety in host names you need to beat the connection limit.

]]>