Closing with an additional comment that doing mod.stats shm is locking shared memory
access and it is rather lengthy process in a loaded server with a lot of shm usage (it
needs to do grouping for all allocated chunks under shm lock), therefore this is not
recommended at all to execute it often, but rather avoid it. Better get the overall shm
stats and in case one discover a potential leak or unexpected large use of shm, then
leverage mod.stats shm to find the source of the behaviour.
The commits are in master branch, I am not sure yet if they should be backported, the
design of those commands seemed to be more for troubleshooting (run it when out of memory
to get the reports and then restart), rather than runtime continous monitoring (the above
commits try to fix it, but due to lack of extensive testing there can be side effects,
thus not rushing to backport changes related to memory manager interaction). For now, just
avoid using these rpc commands.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/2460#issuecomment-694775225