[NBLUG/talk] slashdotting

[Eric Eisenhart]

On Fri, Apr 18, 2003 at 11:45:07AM -0700, error wrote:
> So if you were about to be slashdotted, what would you do to your
> webserver?

Remove all <img> links.

Change everything dynamic to static.  Particularly on the front page and the
page being linked to from slashdot.

Shrink anything any other way that you can.

Limit Kilobytes required to serve the content.  Limit hits required to
server the content.  Optimize HTML.  Don't use frames.  etc.

For serving static content, whatever server you have can probably fill up a
good-sized pipe quite easily.  Killing the images will help make sure that 

My measly 768K/384K DSL got slashdotted once...  
( http://slashdot.org/article.pl?sid=00/11/23/162232 -- no longer on my DSL,
but was at the time).  Luckily for me, I was out of town at the time, so I
just heard about it later...

Also, very helpful: try to see if you can convince the /. post to be
properly descriptive.  The vague and inaccurate stuff that frequently ends
up in the bit on /. will encourage people to follow the link to figure out
what's actually being said; the better it's said there, the more people will
just read the /. bit without clicking.
-- 
Eric Eisenhart
NBLUG Co-Founder & Vice-President Pro Tempore
The North Bay Linux Users Group
http://nblug.org/
eric at nblug.org, IRC: Freiheit at freenode, AIM: falschfreiheit, ICQ: 48217244