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 to modify it.. This is making next child of parent is getting created with much more shared memory ? Should I leave it or worry about it ? As even if RSS of all(combined) apache processes are increasing if I consider shared dirty in it, it will definitely looks smaller.
On Tue, Sep 16, 2014 at 10:10 PM, Perrin Harkins <phark...@gmail.com> wrote: > 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 < > nageshgurra...@gmail.com> 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 is serving, so when >> everytime it is creating a new child it is sharing all its memory with >> childs and they are getting even more bigger and so on.. >> I am thinking this might be one reason. I decalred a global variable in >> apache startup (so it'll be shared on across all childs), this variable >> will be loaded with huge DB data in one of perl modules(after request >> comes). Will this increase shared dirty of parent ? (After child writes >> into it, it will no longer shared between parent and child., and parent >> shared dirty should get decreased .. right ?) >> At start parent is only 100MB and after some days it's going above 250MB >> and so childs are going above 400M.. >> Can anybody help ? >> >> Thanks, >> Rao. >> > >
