Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Actually we have following setup for our website that gets traffic around the world:

All JS, Images, Photos are stored on a CDN: Cloud Files ("Akamai light" powered).

The WebApp server who send the dynamic content out are located in Switzerland, the average page size is around 14KB (3-5KB after GZip).

70% of the traffic is from North America. Our network latency time is between 105 - 185 ms to the USA (just-ping.com) mostly measured from data centers I think, means a home user will have higher latency.

Would it be a good solution to place a proxy server on east and west coast of the USA in a data center with a good latency (100ms) to us and to serve the dynamic content from WebAPP server to our visitors from the USA from there? Means the proxy server will forward the request to us and send the answer back.

share|improve this question

If you have many cachable contents, it will be much better in terms of response time and bandwidth usage to use a proxy server between your web server and your clients.

The proxy server will server the pages/objects very quickly without contacting the original servers while the cached objects are not expired. Moving the proxy server(s) closer to the client will improve the response time in most cases.

share|improve this answer
    
no, the content from WebApp is not cacheable and it must be taken on every request from the WebApp Server, the Idea was to get better latency time. All data that's cacheable like CSS, JS, Images, Photos is allready on CDN. – Nenad Dec 9 '11 at 17:25

I don't see how the proxy server will help, if all the pages have to be sent from Europe. It's just another hop with no benefits. You already have static resources on a CDN in the USA. If it's only one page hit of up to 180ms and all other resources are cached I think that's probably ok, it's if there's multiple hits on your server that it could be an issue - Ajax counts.

You could: - Move your application closer to your users - If applicable you could have application servers in different countries, either talking to a database in Europe (possibly slower than you have now if it's db heavy) or synchronised databases in each country (more complex but faster). A master DB in Europe with a read replica in the USA may work.

share|improve this answer

IF 70% of the traffic is in US then it would make great sense to place the app server here. From that point using some HA delivery system would be advisable.

I have a set target for experience of under 1 second for my app to service a client. Whatever needs to happen to make that target is my job.

share|improve this answer

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.