Re: high availability

This has been a theory of mine for a bit, and we're looking at doing something similar. How much data are you sending in the cookies? Our cookies are only 20-25 bytes (identifers), so I can't imagine the transfer time is all that much more - but from what you're saying, it adds up. jeremy brand wrote: > Just a little more on high performance. Images & cookie data. > > Keep your images on a seperate machine (with a separate domain). See > how Yahoo does it. The images come from yimg.com. See how we do it: > > http://www.care2.com/ > The images are on > http://dingo.care-mail.com/ > > Here is the reason. Eventually, you will have more and more cookie > data used within your site. Unless there is a reason, and for us > there is none, peoples browsers are going to send all that cookie data > for every image requested if you keep your images on the same domain. > This happens (as we all know, right?) because web browsers send cookie > headers with each request to the given domain+path pair. > > By keeping your images on a separate domain, that cookie traffic is > eliminated -- thus speeding up image loading because the total traffic > between the client and server is minimized. > > By separating images from scripts, that also allows us to run a high > performance web server for images (thttpd) and use Apache for our > scripts. Apache is much more resource intensive, but needed (in > our case) for dynamic data: > > headers from www.care2.com: > Server: Apache/1.3.12 > > headers from dingo.care-mail.com: > Server: thttpd/2.17 10may00 > > So, we have two added benifits which are a tremendous cost+performance > benefit. > > -jeremy brand > http://www.JeremyBrand.com/Jeremy/Brand/Jeremy_Brand.html for > more -- ========================== Michael Kimsal http://www.tapinternet.com 734-480-9961