I see.
I would suggest to maybe activate memory debugging in Kamailio to see if the memory pool is maybe looking different from what you expect. You can get output at shut-down but also during run-time with corex RCP cmds.
--
Henning Westerholt –
https://skalatan.de/blog/
Kamailio services –
https://gilawa.com
-----Original Message-----
From: kthulasizwe@gmail.com
kthulasizwe@gmail.com
Sent: Friday, August 12, 2022 1:21 PM
To: Henning Westerholt
hw@gilawa.com
Cc: Kamailio (SER) - Development Mailing List
sr-dev@lists.kamailio.org
Subject: Re: [sr-dev] Large memory allocation on module startup
Yes, that has been my precise reaction as well.
> On 12 Aug 2022, at 13:14, Henning Westerholt
hw@gilawa.com wrote:
>
> Hello,
>
> but you are saying you are not using the memory? This is really odd, why should it affect performance if the system itself does enough memory.
>
> Cheers,
>
> Henning
>
> --
> Henning Westerholt –
https://skalatan.de/blog/ Kamailio services –
>
https://gilawa.com
>
> -----Original Message-----
> From: kthulasizwe@gmail.com
kthulasizwe@gmail.com
> Sent: Friday, August 12, 2022 1:12 PM
> To: Henning Westerholt
hw@gilawa.com
> Cc: Kamailio (SER) - Development Mailing List
>
sr-dev@lists.kamailio.org
> Subject: Re: [sr-dev] Large memory allocation on module startup
>
> Thanks for the reply,
> So previously under load testing, I could do around 240 registrations per seconds and now it’s only around 180.
>
> Also, forgot to mention, it would perform better (around 228 reps) when the load testing was delayed for 10 to 20 minutes after restarting.
>
>
>> On 12 Aug 2022, at 12:53, Henning Westerholt
hw@gilawa.com wrote:
>>
>> Hello,
>>
>> can you add a bit more details, e.g. before it took x seconds and now it takes y seconds?
>>
>> Some modules (e.g. carrierroute) can allocate quite large shared memory segments during startup, and it should work ok.
>>
>> Cheers,
>>
>> Henning
>>
>> --
>> Henning Westerholt -
https://skalatan.de/blog/ Kamailio services -
>>
https://gilawa.com
>>
>> -----Original Message-----
>> From: sr-dev
sr-dev-bounces@lists.kamailio.org On Behalf Of
>> kthulasizwe@gmail.com
>> Sent: Friday, August 12, 2022 11:04 AM
>> To: sr-dev@lists.kamailio.org
>> Subject: [sr-dev] Large memory allocation on module startup
>>
>> Hi Guys,
>>
>> I have recently modified a custom module, where I now shm_mallocxz 2MB, as part of module start up and this memory is not being used as yet.
>>
>> Previously, the would be smaller chunks(100 bytes at most) shm_malloced during message processing.
>> I have observed significant runtime performance degradation from just this single change. I would appreciate any suggestions/thoughts you might have.
>>
>> Below are some the relevant details.
>>
>> OS:Alpine Linux
>> RAM: 16GB
>> Configured Shared memory: 4GB
>> shm_force_alloc=1
>> Typical shared memory usage: 1.5GB
>> System swapping is disabled, also observed during load testing that no mem is getting swapped.
>>
>>
>> _______________________________________________
>> Kamailio (SER) - Development Mailing List sr-dev@lists.kamailio.org
>>
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-dev