just a followup: i recompiled perl from the redhat
source rpms and it seems to have fixed my memory
leaks.
thanks to everyone for their help
remi.
> Remi Fasol wrote:
> >
> > hi there.
> >
> > i'm having problems with my redhat secure server
> and
> > mod_perl combo
> > (mod_perl as a DSO). i'
On Fri, 22 Oct 1999, Stas Bekman wrote:
> To exit upon request completion
> my $r = shift;
> $r->post_connection(\&exit_child);
> sub exit_child{
> # some logic here if needed
> $r->child_terminate;
> }
no need for all that, just call $r->child_terminate at any point in the
request, apache
Stas Bekman wrote:
>
> Is it a single script/handler you are testing with?
>
> *all* children at once? You mean you do a single request and it happens?
> The only reason I can think of is parent dirtying its memory pages,
> however I cannot think about a possible way to do this...
>
Yes, I rel
> Thanks so much for the tips. I got Apache::VMonitor - awesome package, Stas
> - and investigated it further. What I found was that each child loses a
> small amount of shared memory during normal use, due to copy-on-write. In
> my case from about 12M to 9M (roughly 25%). But it stabilizes at
Randy,
Thanks so much for the tips. I got Apache::VMonitor - awesome package, Stas
- and investigated it further. What I found was that each child loses a
small amount of shared memory during normal use, due to copy-on-write. In
my case from about 12M to 9M (roughly 25%). But it stabilizes at
On Wed, Oct 20, 1999 at 10:47:02PM -0700, Adi wrote:
> > On Wed, 20 Oct 1999, Remi Fasol wrote:
> Does anyone know why the shared memory would decrease so dramatically?
Perl code and data both live in the data segment. As it is used, any time
it writes information into a new chunk of memory, th
> On Wed, 20 Oct 1999, Remi Fasol wrote:
> >
> > thanks for your suggestions...
> >
> > as a test, i set MaxRequestsPerChild to 500, but it
> > didn't help.
> >
> > just out of curosity, could it be that i'm using
> > mod_perl as a DSO? i've seen alot of warnings against
> > that but that's how th
On Wed, 20 Oct 1999, Remi Fasol wrote:
> --- Joshua Chamas <[EMAIL PROTECTED]> wrote:
> > On the apache end, I would recommend setting
> > MaxRequestsPerChild
> > to under 1000, to clean up any memory leaks that
> > accumulate
> > over time.
>
> thanks for your suggestions...
>
> as a test, i se
--- Joshua Chamas <[EMAIL PROTECTED]> wrote:
> On the apache end, I would recommend setting
> MaxRequestsPerChild
> to under 1000, to clean up any memory leaks that
> accumulate
> over time.
thanks for your suggestions...
as a test, i set MaxRequestsPerChild to 500, but it
didn't help.
just out
On the apache end, I would recommend setting MaxRequestsPerChild
to under 1000, to clean up any memory leaks that accumulate
over time.
Also, you should look into using Apache::ASP->Loader() to
precompile your asp scripts in your parent process, this has
large CPU & RAM sparing benefits.
Check o
hi there.
i'm having problems with my redhat secure server and
mod_perl combo
(mod_perl as a DSO). i'm new to mod_perl (and system
administration) but
obviously am looking forward to getting everything
figured out.
i believe there is some kind of memory leak (not sure
exactly), but when
i start
11 matches
Mail list logo
