Help Stress Test The New Slashdot
Here's you chance to generate wasteful http traffic without even having to run unpatched IIS! We're ready to test Banjo, our new fancy setup w/ new code and new hardware. We plan to keep testing until we think
the system is ready. You are also welcome to submit Bug Reports, although it would be helpful if you skimmed the list of bugs before submitting new ones so we don't have 300 of you tell us that your user info page has other people's comments listed on it again. The new hardware is mostly in place, but the code hasn't been fully optimized yet, so run your wgets... write your bots... whatever makes you happy, but please don't be malicious: just try to load and submit web pages. And don't be surprised, its gonna go up and down like a yo yo as we fix things.
Bug Report: There are no stories or comments. Don't know how that made it through the rigorous testing process...
Got Rhinos?
For god sake, how many people have to point out that its been Slashdotted! Does everyone have the memory span of a goldfish and forget the comment they read 7 seconds ago?!?!
Is http://banjo.slashdot.org/ slashdotted already?
Chortle chortle snigger snigger
Didn't we do this two weeks ago? (Score:-1, Redundant)
std::disclaimer<std::legalese> sig=new std::disclaimer; sig->dump(); delete sig;
Yes, it appears that Banjo has been slashdotted. I just tried to load the page, and it times out. I even tried to telnet to Banjo's port 80 (which is, BTW, the HTTP port), and I get no response. Normally, telnet will say "Connected", and then you can type "GET /" which will fetch the default page. But right now, telnet just says "Trying 64.28.67.73..." which means that Banjo is not completing the TCP handshake. That typically means that the machine is down, or that the machine is so busy, it can't handle any more connections on that port. Sometimes you'll even get a "connection refused" message. But right now, it just sits there.
Only posted minutes ago, and Slashdot has already become the victim of itself? Or is it not loading for other reasons?
Leave it to slashdot to /. itself :)
I can't get to the site :(
garc
The first time you posted this test, it got slashdotted... now banjo is goin real slow.. poor ol banjo.
Come on guys! Give us a bit more info than that. Whats the hardware setup? We want to hear all about the lovely geeky hardware setup and drool uncontollably. Anyone got any ideas?
Looks like Banjo got Slashdot'ed. Does that qualify as a bug?
already! anyone got mirrors?
You know it's bad when Slashdot can't handle the Slashdot effect.
Got Rhinos?
Well, it looks like we've already slashdotted Banjo. Didn't take very long. Maybe you shouldn't switch yet.
Does this mean Banjo has been slashdotted?
...would this be an example of the "Metaslashdot Effect"?
Posted by CmdrTaco on Thursday August 16, @12:13PM
from the bring-it-on dept. Here's you chance to generate wasteful http traffic without even having to run unpatched IIS! We're ready to test Banjo, our new fancy setup w/ new code and new hardware. We plan to keep testing until we think the system is ready. You are also welcome to submit Bug Reports, although it would be helpful if you skimmed the list of bugs before submitting new ones so we don't have 300 of you tell us that your user info page has other people's comments listed on it again. The new hardware is mostly in place, but the code hasn't been fully optimized yet, so run your wgets... write your bots... whatever makes you happy, but please don't be malicious: just try to load and submit web pages.
"you fucking worthless piece of dessicated dog shit. go suck on a diseased homophobic puss-dripping cock and anal-fuck youself with three feet of rusty razor wire."
"desiccated". It's spelled "desiccated".
Too bad it's /.'ed already.
There is no reasonable defense against an idiot with an agenda
:wq
The connection was refused when attempting to contact banjo.slashdot.org
It feels so existential.
"He was a wise man who invented beer." -- Plato
...but it seems to be failing the load tests already.