Knowledgebase: Site Functions
Surviving the Digg Effect
Posted by - NA - on 18 May 2009 02:12 PM

Aren't familiar with this term? See what the 'Digg Effect' really is.

To survive the 'Digg Affect' you need to arm yourself. Check out what you can do to safeguard your site...

The big thing to do on your end is to make this article as fast to serve up as possible. The best way to do that is to make it a static HTML file, rather than part of the Drupal, Joomla, WordPress, etc. site you have now. That can be served *way* faster than a PHP file, especially something relatively intensive like Drupal, Joomla, WordPress, etc.

Also, removing any external file requirements, like images or CSS files, are also crucial to making it speedy, as they'll reduce the number of requests on the machine. In fact, the optimal thing to do is to make a post on your site linking to this static file and having all the content, CSS, and JavaScript (if any) stored within the single file itself. The webserver should definitely be able to keep up with that.

The webserver is really fast at serving up static files, but each individual request adds to the load on the machine. That's a separate TCP/IP connection, a separate webserver process that must be run, and a separate read from the disk. So, each time you include an image or CSS file or Javascript file or whatever in the page, that increases the number of hits on the server by 1. So, if you have a static HTML file by itself, that might be 40 requests per second under a heavy digging. Just add 3 images, and you're suddenly up to 160 requests per second.

(402 vote(s))
This article was helpful
This article was not helpful

Comments (0)
Post a new comment
 
 
Full Name:
Email:
Comments:
Help Desk Software by Kayako fusion