Comments on: Why Everyone Should Use A Content Delivery Network http://blog.revahealth.com/2009/05/why-everyone-should-use-a-content-delivery-network.html Tech, Marketing, Health 2.0 and stuff from the RevaHealth.com team Sat, 21 Nov 2009 04:42:56 +0000 http://wordpress.org/?v=2.8.6 hourly 1 By: Eamonn http://blog.revahealth.com/2009/05/why-everyone-should-use-a-content-delivery-network.html/comment-page-1#comment-419 Eamonn Mon, 08 Jun 2009 14:05:21 +0000 http://blog.revahealth.com/?p=356#comment-419 Here's an interesting and readable article from ACM about the physical limits of networks, Makes good reading as we rush to throw everything into the Cloud http://queue.acm.org/detail.cfm?id=1530063 Here’s an interesting and readable article from ACM about the physical limits of networks, Makes good reading as we rush to throw everything into the Cloud
http://queue.acm.org/detail.cfm?id=1530063

]]> By: admin http://blog.revahealth.com/2009/05/why-everyone-should-use-a-content-delivery-network.html/comment-page-1#comment-382 admin Tue, 02 Jun 2009 11:06:33 +0000 http://blog.revahealth.com/?p=356#comment-382 Hi Simon Thanks for the link to the Yahoo resource, it is excellent and good hint on incrementing the path rather than the files names. Regarding the DNS latency, we have found that these tend to be done in parallel, however they are much longer than we expected, presumably because they aren't cached by the local DNS server to the client. Hi Simon

Thanks for the link to the Yahoo resource, it is excellent and good hint on incrementing the path rather than the files names. Regarding the DNS latency, we have found that these tend to be done in parallel, however they are much longer than we expected, presumably because they aren’t cached by the local DNS server to the client.

]]> By: Simon http://blog.revahealth.com/2009/05/why-everyone-should-use-a-content-delivery-network.html/comment-page-1#comment-364 Simon Wed, 27 May 2009 11:52:46 +0000 http://blog.revahealth.com/?p=356#comment-364 Depending on how many CSS and JS files you use, and your build system, you may find it easier to increment an element in the path to the files rather than the filenames themselves. e.g. http://cdn.example.com/v1.2/style.css Also, be careful not to go overboard on multiple sites to maximise concurrent downloads, each DNS lookup also has a latency. For more tips and discussion, try the always excellent <a href="http://developer.yahoo.com/performance/rules.html" rel="nofollow">Yahoo Performance pages</a>. Depending on how many CSS and JS files you use, and your build system, you may find it easier to increment an element in the path to the files rather than the filenames themselves. e.g. http://cdn.example.com/v1.2/style.css

Also, be careful not to go overboard on multiple sites to maximise concurrent downloads, each DNS lookup also has a latency.

For more tips and discussion, try the always excellent Yahoo Performance pages.

]]>