sr-dev August 2023

sr-dev@lists.kamailio.org

15 participants
203 discussions

by Daniel-Constantin Mierla

Module: kamailio Branch: master Commit: 9fba67792382b53ccd4851764505ee3b119531b1 URL: https://github.com/kamailio/kamailio/commit/9fba67792382b53ccd4851764505ee3… Author: �� <git-dpa(a)aegee.org> Committer: Daniel-Constantin Mierla <miconda(a)gmail.com> Date: 2023-08-07T15:32:56+02:00 docs/ : typos --- Modified: INSTALL Modified: doc/docbook/catalog.xml Modified: doc/docbook/dep.xsl Modified: doc/docbook/entities.xml Modified: doc/docbook/html.chunked.xsl Modified: doc/doxygen/main.dox Modified: doc/man/kamailio.cfg.5 Modified: doc/misc/HISTORY Modified: doc/misc/NEWS Modified: doc/misc/TODO Modified: doc/misc/cvs-commit-rules.txt Modified: doc/stylesheets/dbschema_k/catalog.xml Modified: doc/stylesheets/dbschema_k/xsl/db_berkeley.xsl Modified: doc/stylesheets/dbschema_k/xsl/db_redis.xsl Modified: doc/stylesheets/dbschema_k/xsl/dbtext.xsl Modified: doc/stylesheets/dbschema_k/xsl/mysql.xsl Modified: doc/stylesheets/dbschema_k/xsl/pi_framework_mod.xsl Modified: doc/tutorials/presence/cfg/ps.cfg Modified: doc/tutorials/presence/install.xml Modified: doc/tutorials/presence/intro.xml Modified: doc/tutorials/serdev/routing_engine.xml Modified: doc/tutorials/seruser/otherapps.xml --- Diff: https://github.com/kamailio/kamailio/commit/9fba67792382b53ccd4851764505ee3… Patch: https://github.com/kamailio/kamailio/commit/9fba67792382b53ccd4851764505ee3…

9 months

Re: Performances issue when freeing shared memory in custom module (Kamailio 5.5.2)

by Henning Westerholt

Hello, (Adding sr-dev to CC) This looks indeed a bit strange. Do you get any error messages in the log? In which process you are freeing the memory, one of the worker processes or the RPC process? You could also try to use another memory manager to see if you get better performance. There is a command line parameter to choose one during startup. Cheers, Henning -- Henning Westerholt - https://skalatan.de/blog/ Kamailio services - https://gilawa.com<https://gilawa.com/> From: Chaigneau, Nicolas <nicolas.chaigneau(a)capgemini.com> Sent: Wednesday, January 18, 2023 6:49 PM To: Kamailio (SER) - Users Mailing List <sr-users(a)lists.kamailio.org> Subject: [SR-Users] Performances issue when freeing shared memory in custom module (Kamailio 5.5.2) Hello, I'm encountering performance issues with Kamailio (5.5.2). I'm using a custom Kamailio module that loads routing data in memory, using Kamailio shared memory. This routing data is very large. It can be fully reloaded through a Kamailio RPC command (which is done once each day). When reloading, two sets of data are maintained, one "loading" and another "current" (the latter being used to handle SIP requests). When loading of the new data is finished, it is swapped to "current". Then, memory of the old (now unused) data is freed. I've noticed that when Kamailio is freeing the old data, there is a very significant performance impact on SIP requests. This is surprising to me, because the SIP requests do not use this old data. This is not a CPU issue, idle CPU% is at about 99% at that moment. I'm using the following functions : - shm_mallocxz - shm_free From what I understand, shm_free is actually "qm_shm_free" defined in "src\core\mem\q_malloc.c" (the default shared memory manager being "qm"). I've noticed that there is also a variant shm_free_unsafe ("qm_free"), which does not perform locking. I'm wondering if the lock could be the cause of my performances issues ? (But I'm not sure how this could be possible, because although the SIP requests need to access the shared memory allocated, they do not use directly the functions from the share memory manager.) If the performances issues are causes by the lock, could I use the unsafe version "safely" ? (considering that it is guaranteed that the old data cannot be used by anyone else) Thanks for your help. Regards, Nicolas. This message contains information that may be privileged or confidential and is the property of the Capgemini Group. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain, copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message.

9 months, 1 week

[kamailio/kamailio] Kamailio sending CCR TERMINATE request without waiting for the CCR INITIAL request response (#2143)

by harishyadav1465

**Description** We are using ims_charging module and Freediameter as diameter server for billing process....recently we faced one issue...For Initial **INVITEs** kamailio sending **CCR request (INITIAL_REQUEST)** to **diameter server** but if we receive Immediate **CANCLE** for the **INVITE**, kamailio sending **CCR request ( TERMINATE_REQUEST )** without waiting for the **CCR request (INITIAL_REQUEST) response** from the **Diameter server.**.. **Expected behavior** Kamailio has to send **CCR request ( TERMINATE_REQUEST )** after getting the **response** from the **INITIAL_REQUEST.** **Additional Info** kamailio server : 4.2 platform : linux -- 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/2143

9 months, 1 week

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

sr-dev August 2023