15 Aug
2012
15 Aug
'12
5:07 p.m.
We now seem to be experiencing problems with Kamailio running out of
memory after a period of time running our soak test. After dumping the
shared memory I can see that there is no memory leak, but the problem is
that memory is hugely fragmented with all the free blocks being less
that 10k in size, which is too small for the tcp buffer it is trying to
allocate memory for.
We've noticed that there is a new kamailio runtime option mem_join that
by default is 0. Was the previous default dehaviour the equivalent to
this being set to 1?
Thanks
Paul
15 Aug
15 Aug
5:11 p.m.
Hello,
no, memory join was not enabled before. It was changed from a compile
time option (define) to a global parameter.
Try with mem_join=1. I would like to see the results, as I couldn't
really conduct extensive testing for it. If it looks good, we can even
consider setting it 1 by default.
Cheers,
Daniel
On 8/15/12 4:07 PM, Paul Pankhurst wrote:
We now seem to be experiencing problems with Kamailio
running out of
memory after a period of time running our soak test. After dumping the
shared memory I can see that there is no memory leak, but the problem
is that memory is hugely fragmented with all the free blocks being
less that 10k in size, which is too small for the tcp buffer it is
trying to allocate memory for.
We've noticed that there is a new kamailio runtime option mem_join
that by default is 0. Was the previous default dehaviour the
equivalent to this being set to 1?
Thanks
Paul
_______________________________________________
sr-dev mailing list
sr-dev(a)lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev
--
Daniel-Constantin Mierla - http://www.asipto.com
http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
Kamailio Advanced Training, Seattle, USA, Sep 23-26, 2012 - http://asipto.com/u/katu
Kamailio Practical Workshop, Netherlands, Sep 10-12, 2012 - http://asipto.com/u/kpw
16 Aug
16 Aug
7:05 p.m.
Hi Daniel
I've done some testing with mem_join=1 and the results are very good, we
will certainly be running our config with this set.
What I'm slightly confused about, is why we had not seen problems before
if the default fuctionality is unchanged !?
Paul
On 15/08/2012 15:11, Daniel-Constantin Mierla wrote:
Hello,
no, memory join was not enabled before. It was changed from a compile
time option (define) to a global parameter.
Try with mem_join=1. I would like to see the results, as I couldn't
really conduct extensive testing for it. If it looks good, we can even
consider setting it 1 by default.
Cheers,
Daniel
On 8/15/12 4:07 PM, Paul Pankhurst wrote:
We now seem to be experiencing problems with
Kamailio running out of
memory after a period of time running our soak test. After dumping
the shared memory I can see that there is no memory leak, but the
problem is that memory is hugely fragmented with all the free blocks
being less that 10k in size, which is too small for the tcp buffer it
is trying to allocate memory for.
We've noticed that there is a new kamailio runtime option mem_join
that by default is 0. Was the previous default dehaviour the
equivalent to this being set to 1?
Thanks
Paul
_______________________________________________
sr-dev mailing list
sr-dev(a)lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev
4484
days inactive
4485
days old
2 comments
2 participants
participants (2)
-
Daniel-Constantin Mierla -
Paul Pankhurst