On 25 Apr 2001, Joe Schaefer wrote:
> Kurt George Gjerde <[EMAIL PROTECTED]> writes:
Hi,
> Even if your script were coded perfectly, it is still possible for this
> to happen in modperl.
> Personally, I would consider an average growth rate of only .5kB/hit
> absolutely wonderful :)
As far I
Hi all,
On Wed, 25 Apr 2001, Remco Schaar wrote:
> It is very hard to write perfect code,
True, but it's not hard to write code that doesn't leak memory.
void *p = NULL;
...
...
if( p ) { exit(POINTER_ERROR); }
void *p = malloc(n);
...
...
free( p );
p = NULL;
...
...
By which I mean that I u
On Wed, 25 Apr 2001, G.W. Haywood wrote:
> Hi all,
>
> On Wed, 25 Apr 2001, Remco Schaar wrote:
>
> > It is very hard to write perfect code,
>
> True, but it's not hard to write code that doesn't leak memory.
>
> void *p = NULL;
> ...
> ...
> if( p ) { exit(POINTER_ERROR); }
> void *p = malloc(n)
Kurt George Gjerde <[EMAIL PROTECTED]> writes:
> Each time a page is downloaded the Apache service process claims more
> memory. Well, not each time but like for every 20th download the task
> manager shows Apache using 20-30K more...
>
> A test showed that reloading the same page 2000 times rai
On Wed, Apr 25, 2001 at 10:02:06AM -0400, Brendan McAdams wrote:
Our application performance actually
> improved across the board when we implements MaxRequests... (This
Do you have numbers to back this up? How does reading in a new
script every now and then IMPROVE anything compared to keep
It sounds like you are globalising some variables and never freeing
them, to start with. You definitely need to run in strict and keep your
namespaces managed lest you have processes keep variables in Memory.
I've found that setting MaxRequestsPerChild in apache to a reasonable
amount minimises