Hi,
I am new to mod perl environment so this may looks naive.
Recenlty I observed my apache processes are getting huge.. When I tried
to dig this down I found apache parent process (rss memory , mainly shared
dirty) itself is increasing with number of requests it is serving, so when
everytime
Nageswara rao Gurram wrote:
Hi,
I am new to mod perl environment so this may looks naive.
Recenlty I observed my apache processes are getting huge.. When I tried
to dig this down I found apache parent process (rss memory , mainly shared
dirty) itself is increasing with number of requests it
Hi,
Loading data in the parent process is a common strategy for data that you
won't modify. Do you need to change this data from the child processes? If
so, does it matter if the other child processes see the changes?
- Perrin
On Tue, Sep 16, 2014 at 10:28 AM, Nageswara rao Gurram
System details:
CentOS release 5.9, Apache/2.2.23,Perl 5.8.8, mod_perl 2.0 and
Apache is running with pre-fork config.
On Tue, Sep 16, 2014 at 8:18 PM, André Warnier a...@ice-sa.com wrote:
Nageswara rao Gurram wrote:
Hi,
I am new to mod perl environment so this may looks naive.
Hi,
I am modifying(infact intializing) the global variable declared in start
up with child processes..When every child process tries to modify it I
think it should come as private memory of child.. But I am wondering why
shared dirty memory of parent process is increasing every time child tries
Hi.
This is a bit beside your question below (for which I do not know the answer
anyway).
But if it is the case
- that you have a number of Apache child processes which all need at start a certain
initial table of data of 100-200 MB in size
- that each of these children is going to modify
