Noticed a small “burp” in Sitepoints availability yesterday evening. Then got tipped off about this and all made sense.
And of course there’s the inevitable flame war which happens every time someone mentions PHP on /. but the quality of flame is definately on the rise like this – Gnu/PHP/Linux – now there’s an idea.
Hadn’t seen this before but being slashdotted even has an entry on Wikipedia.
{ 9 comments }
August 9, 2004 at 11:58 pmWell, I don’t think there are that many languages that could take a full on /. without croaking. It’s all about the numbers.
Feedster got /. when it was early in development and Scott managed to survive the onslaught with mod_throttle – look into it, it will save you life.
Now, there is one more problem, can you afford the bandwidth? :)
August 9, 2004 at 10:48 pmAnother Slashdot review, (of Volume II) went up today, here
August 8, 2004 at 11:19 amwhy so many negative comments on slashdot?
sheesh, talk about ignorance.
wd on being /.-ed though
August 7, 2004 at 12:32 amA PHD thesis on being \.-ed :) Woww – three hundred something pages!
August 6, 2004 at 11:20 amAlways good to use AB ( http://httpd.apache.org/docs/programs/ab.html ) on your server to see what it can take when it comes to /.ing
Mamboserver have a nice thread on various CMS and what load average they came out with under heavy load: http://forum.mamboserver.com/showthread.php?t=11782
August 6, 2004 at 9:52 amIt gets me to raise some question: – How do you make sure you develop you site to handle very high number of request? – Are there any design/coding practices?
There’s not a quick answer to one (except perhaps cache dynamic content) – best resource I’ve seen is Advanced PHP Programming – blogged my thoughts on it here.
- In the event of being “slashdotted”. – How do you cope with it? (can you cope with it). Strategies? – Can there be any problems with your service provider? (because your site is overloading their server) How to resolve them? – Are there any signs it’s happening?
On a shared host, it’s a problem if PHP is running under Apache (a recent trend with hosts seems to be switching to PHP/CGI so you have a better idea who’s site is the problem).
A general self defence might be to prepare an output cache you can implement with a quick change, making sure all content is static for the period of the /. “attack”. You can probably do this easily with the PHP ini settings auto_prepend_file, auto_append_file plus output buffering (perhaps PEAR::Cache_Lite).
August 6, 2004 at 9:40 am(sorry for the double post)…
It gets me to raise some question:
– How do you make sure you develop you site to handle very high number of request?
– Are there any design/coding practices?
- In the event of being “slashdotted”.
– How do you cope with it? (can you cope with it). Strategies?
– Can there be any problems with your service provider? (because your site is overloading their server) How to resolve them?
– Are there any signs it’s happening?
August 6, 2004 at 9:33 amwow…. I had never heard about that slashdot effect…
Make sense altough… I mean we all talk about making sure our own websites are referred as much as possible to get more traffic….
August 6, 2004 at 8:37 amI first thought the guy was serious..
“Perl’s biggest difficulty, as we all know, is the fact that it is by far
one of the slowest languages in existance, especially when compared to
more modern languages such as Basic and HTML.”
Then I understood it was a joke :
“Having just gotten off the phone with Mr. Alan Cox, I can say that he is quite thrilled with the speed increases that
will occur when the Linux kernel is completely rewritten in PHP.” ROTFL
Comments on this entry are closed.
