On Thu, 2008-03-20 at 08:43 +0000, Hegde, Ramesh (OpenCall) wrote: > Hello Steve, > > You can retroduce it easily with test/publish.c program. Modify the > program and add a sleep(60) before saEvtFinalize. Run the top -p > <aisexec pid> on one window and run publish on other window. When it > is publishing , the memory of aisexec will increase from 15m to 17m. > Even when it stops publishing (sleeping), memory will still be 17m. > Memory will reduce to 15m again when saEvtFinalize is invoked from > client side. This is surely a bug in openais. This will happen with > any version of openais. > > Let me know if you need any help in reproducing the issue.
Ramesh, Each IPC connection consumes two megabytes of ram. So each SaEvtInitialize you make to aisexec will consume two mb of ram. The idea is you only really need to call this once so the memory usage would not be significant compared to the rest of the system. This can be reduced by reducing the maximum memory size for a message. This define is MESSAGE_SIZE_MAX in _______________________________________________ Openais mailing list [email protected] https://lists.linux-foundation.org/mailman/listinfo/openais
