Yes, $xavp(s) are bound to the transaction, like the $avp. About the memory fragmentation - the memory manager should re-use fitting memory blocks, but this depends on the overall traffic to the server. In general, if you use a recent kamailio version, we activated the memory defragmentation some time ago. This should reduce the number of fragements. You can check with the shm stats. On old servers you can activate with a core parameter.
Cheers, Henning -- Henning Westerholt – https://skalatan.de/blog/ Kamailio services – https://gilawa.com -----Original Message----- From: sr-users <[email protected]> On Behalf Of Alex Balashov Sent: Monday, June 29, 2020 10:31 PM To: [email protected] Subject: Re: [SR-Users] Sql_result_free() not cleaning properly On 6/29/20 4:27 PM, Henning Westerholt wrote: > I guess you are using sql_xquery? The sql_free_result will only free a > native sql result in script, not the xavp. But the XAVP goes out of scope once the transaction to which it pertains expires, right? And accordingly should be freed? (This also leads one to wonder: if the same XAVP name is referenced in a subsequent sql_xquery() call in the course of processing the same message, will it free and re-allocate memory for a new PV, perhaps contributing to unnecessary fragmentation? Or will it simply reuse the SHM block for the previously allocated PV?) -- Alex -- Alex Balashov | Principal | Evariste Systems LLC Tel: +1-706-510-6800 / +1-800-250-5920 (toll-free) Web: http://www.evaristesys.com/, http://www.csrpswitch.com/ _______________________________________________ Kamailio (SER) - Users Mailing List [email protected] https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users _______________________________________________ Kamailio (SER) - Users Mailing List [email protected] https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
