Hi Ramesh, aisexec locks all the pages in memory due to which all the pages of the executable are loaded in the memory. This is the reason for initial 15MB space consumption.
However, I am not sure why event activities are making the memory grow. It could be some memory leak. Try the following and see what is the behavior: You will find aisexec_mlockall() function in main.c file. Comment this function. Also this function is invoked from main() function. You need to comment that as well. This will make aisexec() not to lock all the pages in memory. Try this and see the behavior. Regards, Shridhar On Tue, 2008-03-18 at 07:11 +0000, Hegde, Ramesh (OpenCall) wrote: > Hello Steve > > > > We have observed the following behavior with aisexec daemon. Note that > we are using only event service from openais. > > > > · The aisexec process uses about 15M of resident memory just > after startup. > > · After sending several Events , the amount of resident memory > used by aisexec process is about 500M > > · Some aged instance of this process using about 1.2GB > > > > Such resource consumption of this process sounds abnormal. We are > using openais version openais-0.80.3-2. > > > > Have you seen such behavior earlier? Is there anything else we need to > do to avoid this kind of issue? > > > > Thanks in Advance > > Regards > > Ramesh > > > > > > > > Ramesh Hegde > > Software Engineer, Hewlett Packard > > > India Software Operations Pvt. Ltd > > > Sy No 192, Whitefield Road > > > Mahadevapura Post > > > Bangalore - 560 048. India. > > > +91 80 2516 6486- Direct > > > +91 80 2513 3522 - Fax > > > Jabber Id : [EMAIL PROTECTED] > > > +hp = everything is possible > > > > > _______________________________________________ > Openais mailing list > [email protected] > https://lists.linux-foundation.org/mailman/listinfo/openais _______________________________________________ Openais mailing list [email protected] https://lists.linux-foundation.org/mailman/listinfo/openais
