httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dean Gaudet <dgau...@arctic.org>
Subject Re: worth fixing "read headers forever" issue?
Date Fri, 02 Jan 1998 21:22:11 GMT


On Fri, 2 Jan 1998, Brian Behlendorf wrote:

> Watching the size of the pool and subpools, if it's efficient, sounds great
> to me.  

We actually don't have to watch the size of pools and sub_pools.  We need
only instrument malloc_block().  When it malloc()s a block it increments a
scoreboard entry showing how much memory it has allocated.  The parent
prefers to kill off the child with the most memory allocated.  It's not at
all expensive actually. 

This works fine until/unless there's code using a lot of 3rd party library
routines which use malloc()/free() dynamically during hits.  So the child
might want to periodically call getrusage() to update its memory allocated
figure.  This is a bit more expensive (and less portable). 

Dean



Mime
View raw message