Re: [Ids-devel] IDS performance / mod-perl?

[Techwolf <Tec...@at...>]

At 05:42 PM 10/17/2001 -0400, Jeff wrote:
>         512M is not as much memory as it seems with modperl because each 
> httpd child can chew up many
>double-digit megs of memory.  I don't use modperl on servers with less 
>than a gig.  It really depends
>on how much traffic httpd is getting (how many children are spawned), how 
>frequently IDS is called, how
>often the children are killed off, and some other things.  Particularly 
>with the imagemagick stuff,
>which uses oodles of memory when processing images, IDS has the potential 
>to go through quite a bit of
>memory.  If nothing else, set your MaxRequestsPerChild value very low 
>(like single digit).

I got DoS by someone using GoZilla. It spawn enough processes at once that 
nearly 200M of swap was used up. Slowed the system to a keystroke a minute 
until I finally manage to kill httpd. Now I have child settings to a lot 
less then the default of 25. Currently at fixed 15 as that seems to a good 
setting for it. No swap used and somewhat faster service as childs does not 
have to spawn as its already in memory. I've tried 5 when I had less 
memory, but that was only handling two clients as most users are using 
keep-alive and that will tied up a connection until it times out. IE is 
defaulted to two keep-alive connections and four non-keep-alive connections.

Would be nice if IDS had a max memory setting. *grins* Don't flame me, I 
know how nearly impossible that is with the current setup. Perhaps have IDS 
NOT call imakic for every hit as I think Imagic is the one chewing up the 
most resources.


Techwolf
Tec...@at...
http://www.techwolf.net/index.html
PGP public keys on web site.