Data center which hosts servers for a website plays a significant role in the performance of the website. There are few things which should be kept in mind before choosing a data center:
1) Measuring distance in terms of hops is not the best approach. Latency is the accurate measure of speed on the internet and should be considered over the physical distance (hops). Thus, a data center closest to your customer might not be the fastest. Check latency of multiple data centers before choosing one. Latency can be tested by simply performing ping/traceroute tests to any server already hosted on the data center.
2) Check latency from regions which represent majority of the website's audience locations. So, if your site will cater to a specific region (like a city or state) then measure latency from only that region. If your site caters to a distributed audience (throughout the country or across continents) then test the latency from regions where you expect the maximum traffic.
3) Choose a ISP neutral data center. Data centers run by an ISP will perform really well with clients using the same ISP but might not be great when connecting with other ISPs.
Showing posts with label sysad. Show all posts
Showing posts with label sysad. Show all posts
Wednesday, August 04, 2010
Website Performance: Reverse Proxy for Spoon Feeding
When clients with slow internet connection request a page, the server holds on to the thread/process till the complete response is transferred. This results in resources holding up for longer than in cases where clients use fast connections.
To handle this, a reverse proxy (like squid, nginx etc.) can be used in front of the web server. The web server will simply need to transfer content to the reverse proxy (which is super fast as they are on the same network).
The reverse proxy takes the burden of transferring the response slowly and frees the web server immediately.
To handle this, a reverse proxy (like squid, nginx etc.) can be used in front of the web server. The web server will simply need to transfer content to the reverse proxy (which is super fast as they are on the same network).
The reverse proxy takes the burden of transferring the response slowly and frees the web server immediately.
Website Performance: Web Server for Static Content
This approach is useful if you are not using a CDN to render static content (like js,css and images).
Servers which are used for the application (like Apache or Tomcat) are great for requests which require execution of some code before rendering the page.
There are a bunch of light weight web servers (like lighttpd, varnish and nginx) which are tuned to render static content really fast.
There are a bunch of benchmarking results out there. You will see clear benefits when a page with multiple static objects is rendered with any of these light weight web servers.
Servers which are used for the application (like Apache or Tomcat) are great for requests which require execution of some code before rendering the page.
There are a bunch of light weight web servers (like lighttpd, varnish and nginx) which are tuned to render static content really fast.
There are a bunch of benchmarking results out there. You will see clear benefits when a page with multiple static objects is rendered with any of these light weight web servers.
Tuesday, August 03, 2010
Website Performance: Use CDN Effectively
In most cases, we consider using a CDN (like Akamai) for static content like images stylesheets and JavaScript whereas ignore it for the HTML content.
Certain HTML might be cacheable. For example, if a certain HTML page changes every hour, for one hour it remains constant. It will be great if this page can be cached by the CDN somehow so that the first request from a region enables the CDN to cache it for the whole region.
The CDN is configurable for your site. Once you access the configuration, there should be options like:
1) Cache content on the edge server basis the cache headers sent by origin OR
2) Cache certain file/folder/url for X minutes/hours
It's imperative to understand and configure the CDN for optimal performance.
Certain HTML might be cacheable. For example, if a certain HTML page changes every hour, for one hour it remains constant. It will be great if this page can be cached by the CDN somehow so that the first request from a region enables the CDN to cache it for the whole region.
The CDN is configurable for your site. Once you access the configuration, there should be options like:
1) Cache content on the edge server basis the cache headers sent by origin OR
2) Cache certain file/folder/url for X minutes/hours
It's imperative to understand and configure the CDN for optimal performance.
Subscribe to:
Posts (Atom)