Slashdotting takes out Apache, and I would put Apache 2.X at orders of magnitude better than any MOO softcode http server.
I think this is a bit of an exaggeration. I know of quite a few Apache servers that have survived a slashdotting. The connection bandwidth is most often the cause of death - low bandwidth leads to slow connections, slow connections leads to many hanging Apache threads/processes/whatever-depending-upon-configuration, and then the problem quickly grows to kill the server.
That aside, I'd agree with the point here that an HTTP server in the MOO probably couldn't handle a slashdotting. Most often the content is being generated dynamically, the MOO isn't the speediest thing in the world, and it's limited to a single process. I'd bet most MOO servers feel it even when rude search engine spiders hit them with many simultaneous requests.
On 9-Dec-04, at 12:59 AM, The Mage wrote:
The question: how will E_WEB hold up vs. Apache or thttpd under heavy loads? Will the LambdaMOO/E_WEB be the bottleneck? I'll be serving from a 1Mbps upstream ADSL connection at first. If I get a swarm of hits, which piece do you think is likely to choke first?
I'd guess that it depends upon the content being served. If the MOO server is just pumping out the contents of properties, then the DSL connection would go first. If it's doing anything that takes long enough to suspend(), ... well, either way, you can likely handle a reasonable amount of traffic, up to a few hits per second.
-- Mathieu Fenniak <[EMAIL PROTECTED]> http://stompstompstomp.com/
############################################################# This message is sent to you because you are subscribed to the mailing list <[EMAIL PROTECTED]>. To unsubscribe, E-mail to: <[EMAIL PROTECTED]> To switch to the DIGEST mode, E-mail to <[EMAIL PROTECTED]> To switch to the INDEX mode, E-mail to <[EMAIL PROTECTED]> Send administrative queries to <[EMAIL PROTECTED]>
