Thanks, I didn't know about the "top" utility. It looks really useful. I
will use it to see if all my main memory is filled up if/when this
happens again. In fact, I may try some stress testing to purposely flush
out the problem.

What makes you think that the problem is with DBI? That would be a
little worrying. This thing does look like some kind of leak now to me,
perhaps rather than anything to do directly with Embperl. I'll let the
list know what I find out from my testing.

Gerald, if this is Perl not releasing resources on recompile, then that
is something I can handle. I just have to be careful to restart apache
when updating sources. Is this seen as a bug in Perl, I wonder, or is it
accepted behavior?

Thanks again

-Neil

[EMAIL PROTECTED] wrote:
> 
> We are seeing a larger memory leak in our application, and think it may be
> from the DBI layer or our use of it. We tried using Apache:leak, but are not
> sure if that works well with embperl - is that the best thing to use for
> tracking down the leaks?
> 
> Also, "top" works well for monitoring the memory. "M" after it loads sorts
> by memory, and you can see the status of main and virtual memory. We saw the
> slowdown once main memory was filled.
> 
>  -----Original Message-----
> From:   G.Richter [mailto:[EMAIL PROTECTED]]
> Sent:   Thursday, March 22, 2001 8:14 AM
> To:     Neil Gunton
> Cc:     [EMAIL PROTECTED]
> Subject:        Re: Caching question
> 
> > Is it possible that there was some kind
> > of memory leak or other kind of buildup over time, as a result of the
> > rapidly changing html sources?
> 
> Perl will not totaly release all resources when you recompile a script. So
> there is a very small memory leak, that occurs when a script is
> recompiled.Since recompiling doesn't occurs so often (compared to a normal
> requests), that shouldn't be a problem normaly.
> 
> To see if this is really a memory issue, just watch the memory size of your
> httpd child processes (e.g. via ps xau | grep httpd). If it is a memory
> leak, we need to track down from where it comes. I don't expect that Embperl
> is the source, because I always test Embperl for memory leaks before I make
> a new release, but who knows....
> 
> Gerald
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to