|
|
Posted by Nu on 02/01/07 00:54
"Sanders Kaufman" <bucky@kaufman.net> wrote in message
news:ypawh.23974$yC5.18951@newssvr27.news.prodigy.net...
> Nu wrote:
> > Sanders Kaufman" <bucky@kaufman.net> wrote in message
>
> >> But your best bet is to just make sure you have capacity to
> >> handle peak loads, and that overloaded systems throttle down
> >> gracefully.
> >
> > Actually, my site goes to index.php and then index.php digs around in
other
> > PHPs and MySQL. If I stop it right at index.php, I can keep my account
from
> > overloading the CPU.
>
> In that case - you just have to choose one or more methods among
> the several (labor-intensive) ones out there.
>
> You can exit based on IP's - but they can be spoofed. You can
> exit based on other headers - but they can be spoofed, too.
>
> This is why developers talk so much about "scalability". If
> your site isn't designed to handle peak loads, and to exit
> gracefully during overload - all of the other measures won't help.
>
> That's usually an OK design flaw behind a firewall, but not out
> in open water.
So how do I handle peak loads and exit gracefully during overloads?
Basically something like X hits per 10 seconds to index.php sounds simple
enough. I can't find out how to do that, though.
Navigation:
[Reply to this message]
|