Under Fire

By Daniel Miessler on September 14th, 2006: Tagged as Digg | LAMP | Social | Sysadmin

I just got pwned by the Digg effect — for like 15 hours — and I’m still unsure of where the bottleneck was.

Was it MYSQL? Was it Apache? I need to do some research. If it’s my host I’m going to pummel them, and if it’s inefficient code on my server, then I’m going to rectify that. I do know that I could still ping my site while the website was down. I could still SSH to it as well, and get mail.

I’m thinking it has to be AMP based. So embarrassing…I pay good money for a dedicated server, and I should to be able to withstand a Digg effect better than this. This can’t happen again.

If anyone’s a guru on optimizing servers to withstand traffic onslaughts, let me know.

  • Digg
  • Reddit
  • HackerNews
  • StumbleUpon
  • DZone
  • Google Bookmarks
  • Twitter
  • Facebook
  • del.icio.us
  • FriendFeed
  • Posterous
  • RSS
  • email
  

Comments

  • Tim
    The digg effect can be harsh, man. The slashdot effect has been known to take down several sites, and I've heard it's not quite as bad as digg now-a-days.

    Take it as a compliment that you wrote something so cool.
  • Anonymous
    Put a reverse proxy like hginx in front of the server. This is quite easy and helps a lot on amp sytems like yours.
blog comments powered by Disqus

Twitter Microblog

twitter_icon      facebook_icon

Sample Original Content


Information Security

Tutorials and Primers

Culture & Society

Technology & Science

Politics

Philosophy & Religion

Miscellaneous

Tools & Projects


Blog Archives