Forum Moderators: open
If it's not too nosey, would be great if Brett could tell us the reasons for this - is it to reduce some bandwidth from the main server - and how successful has it been.
Does anyone else do what webmasterworld seems to do or know why it's like that?
If you look at it this way - if all of my files were on one hosted server, each page request results in images, css, js etc. files going through the server pipe and taking from my monthly bandwidth allowance.
By having two hosted servers, one page request means that the file calls are split between the two, images (which generally take up the most bandwidth) coming from one sever and everything else coming from the other.
This means that the pull on my bandwidth allowance is spread over two servers and I can make it last longer. Also, as Brett mentioned, you can balance load on the servers in a primitive method this way too.
I can't invision a scenario when you'd ever want anything else. Unfortunatly, many cable and dsl services give their new members instructions on how to disable caching 100% in their browsers. This is good for dynamic content, and lousy for static content (like images). Some browser setups take that to the extreme and reload each and every graphic even if that graphic is a duplicate (such as some browsers, will issue 30-40 requests for the graphics in this thread).
I off load images as well to an image server. It works out great, the access log is much easier to read and parse. It also makes managing images much easier. I like to have one server for the website, one server for the database, one server for the index, one server for mail, etc... it makes managing growth that much easier. If one of those servers gets to much strain I can bring another server online to share the load for that server's job type. An image server doesn't take a lot resources to run, but the website may require two or three servers. Any site that receives over 1 Million visitors a month should think about scaling their operation so it grows properly.