Researching the Slashdot Effect?

leonia asks: "At Columbia University, we are investigating methods and software to automatically deal with sudden, unpredictable load spikes ala the 'Slashdot effect'. We are looking for web sites that have been the 'victim' of this effect who would be willing to share anonymized web logs with us. If you know of a site that went under after it was mentioned on Slashdot or similar site or are the proud owner of such a site, we'd love to talk to you."

Comments

What? No link?

[RQuinn]

I guess we should all try and slashdot the mail server then.

Hah!

[orangesquid]

Smart author... he didn't include any links to Columbia University's pages! ;)

Agenda

[tedDancin]

Slashdot Research Dept. Agenda:

• Investigate Slashdot Effect (in progress)
• Interrogate the 40 Slashdotters we have captured in the 1st lab for continually posting "First Post".
• Cover the 40 "Beowulf Cluster" posting Slashdotters we have in the 2nd lab with mollases and feathers.

We can help

[ajuda]

Everyone, CLICK THIS LINK. Let's give those ivy researchers some first hand data.

Looking for people who have been slashdotted?

[gnovos]

Allow me to introduce you to the Archives.

Sept 11, 2001

[erpbridge]

I would think that a lot of the major news sites like CNN and MSNBC, as well as Slashdot itself, would have some info as to how they held up on Sept 11, 2001. If anything was a Slashdot effect, that day was. (BTW, Slashdot seems to have been the site that best withstood the increased traffic that day... the other major ones crumbled.)

That said, people have written about the same thing, researching the Slashdot effect on their own sites, and posted logs here on Slashdot. I'm too lazy right now, but you may want to search the archives for some info.

Re:naive Question?

[SuiteSisterMary]

Slashdot gets slashdotted regularly. They just know how to handle it.

Ever notice how sometimes, the front page doesn't have your login information? Or the post count doesn't get updated? You're being served a static page for one reason or another.

The simple fact of the matter is that most of the 'database driven' sites, which is where you get the 'mysql socket error' or 'too many sql server connections' or whatever problems, don't need to be database driven. You don't write a static article, put it in a database, then hit that database every bloody time somebody wants to read it. Put a copy in a variable, display that, refresh the variable every five minutes. Or even every minute. Or even ever ten seconds. You'll still never get more than six connections a minute, at that rate, and the information is just as current and fresh.