--- Aaron Stone <[EMAIL PROTECTED]> wrote:
> For some network admins, doing connection throttling
> at the firewall
> will be a great idea. For some system admins, doing
> it from a config
> file will be a great idea ;-)
>
> Poking around for Apache solutions, it looks like
> some people are using
> mod_throttle and mod_bandwidth for Apache 1.3.x.
> Can't find anything for
> 2.0.x, so I guess they must be doing kernel level
> traffic shaping?
>
> On a side note, here's good reading on how Apache
> handles sockets:
>
>
http://httpd.apache.org/docs/1.3/misc/perf-tuning.html
>
http://httpd.apache.org/docs/2.0/misc/perf-tuning.html
>
> In particular, they used to only allow spawning one
> new child per
> second. They say this worked great in real life, but
> sucked in
> benchmarks. So now they allow an increasing number
> -- in consecutive
> seconds, 1 new process, then 2, then 4... up to 32
> processes per second
> until the maxchildren setting is reached.
>
> Aaron
>
> On Fri, 2005-09-16 at 14:10 +0200, Paul J Stevens
> wrote:
> > Isn't this something that rather belongs in the
> firewall?
> >
> > Just a thought.
> >
I would suggest we go for how the Apache 1.3.x
mod_throttle works since not every sys admin can have
access to the router to do it since many ISPs admins
think we should do it in the server level to not
affect their network speed ..etc.
Regards,
-Abdullah
__________________________________________________________
Find your next car at http://autos.yahoo.ca
