[Kamailio-Users] location table

Thu Feb 5 19:41:17 CET 2009

Hi Daniel,

I checked the NW traffic, it's not very high, around 11k pkt/sec coming into
SUT. With the similar amount of traffic, openser has not problem to deal
with call setup/teardown, but not registration. Increasing udp buffer helps
some, but not a lot.

I am using 32 children. When things get wrong, with the error message I
mentioned earlier, I can see messages generated by syslog can be very
large.  This may further degrade the performance and more packets get
dropped.

How much rate do you get for registration? Do you use authentication?

I will try the test with larger hash size.

Thanks,
-Joy

On Thu, Feb 5, 2009 at 10:20 AM, Daniel-Constantin Mierla <miconda at gmail.com
> wrote:

> Hello Joy,
>
> On 02/05/2009 08:07 PM, joy yue wrote:
>
>>
>> Hi Daniel,
>>
>>
>> On Thu, Feb 5, 2009 at 7:29 AM, Daniel-Constantin Mierla <
>> miconda at gmail.com <mailto:miconda at gmail.com>> wrote:
>>
>>    Hello,
>>
>>    are you running kamailio/openser with higher debug mode (e.g.,
>>    debug set to a value higher than 3)?
>>
>>
>> The debug mode I am using is 0, which is set in the .cfg file.
>>
> ok, then is not high at all :-)
>
>
>>
>>
>>    Is your syslog configured asynchronous? I tested registration with
>>    very high rate and there was no performance issue. There is for
>>    sure something misconfigured.
>>
>>
>> I am using solaris. The default mode is synchronous, and actually I don't
>> think solaris support asynchronous write.
>> openser use syslog to log in debugging information, right?
>>
>
> by default yes. Do you get lot of log messages coming from openser in the
> syslog file?
>
>  If the mode matters, can I just simply disable openser from logging in any
>> information to files?
>>
>
> There is compilation to disable all loggings, but it seems that the problem
> is somewhere else.
>
> What is the value of children in your configuration file? Also, try to
> increase the size of the hash table used by usrloc module:
> http://kamailio.org/docs/modules/1.4.x/usrloc.html#id2506464
>
> Can you get stats from the network and see what was the reason for dropped
> packets? Full buffer?
>
> Cheers,
> Daniel
>
>
>
>> thanks,
>> -Joy
>>
>>
>>
>>    Cheers,
>>    Daniel
>>
>>
>>
>>    On 02/05/2009 01:37 AM, joy yue wrote:
>>
>>
>>        Hi Henning/Daniel,
>>
>>        Sorry to take such a long time replying back.
>>
>>        For my rig, I am using the memory as location back-up. When
>>        the issue occurs, I see many registration request sent from
>>        SIPp but not many 200 replies. netstat shows a huge amount of
>>        packets get dropped.
>>
>>        Also I realized the issue only occurs when SIPp tried to
>>        register many users in a very short time. With the same number
>>        of users, the issue goes away if registration rate is kept
>>        lower. When the issue occurs, usrloc module contends lock a
>>        lot calling from new_ucontact(), and many system time is spent
>>        in yield system calls. So it looks more like a performance
>>        issue to me.
>>
>>        Thanks,
>>        -Joy
>>
>>        On 1/27/09, *Henning Westerholt* <henning.westerholt at 1und1.de
>>        <mailto:henning.westerholt at 1und1.de>
>>        <mailto:henning.westerholt at 1und1.de
>>        <mailto:henning.westerholt at 1und1.de>>> wrote:
>>
>>           On Monday 26 January 2009, joy yue wrote:
>>           > Is there a limitation on the number of rows in location
>>        table?
>>           In my rig,
>>           > whatever number of users I use (>2million users), I
>>        notice the
>>           number of
>>           > users in location table is 343707, which is far less than the
>>           number of
>>           > users in my test. I thought previously that location
>>        table saves
>>           all the
>>           > users in my test.
>>           >
>>           > Also when I use large number of users (>2million),
>>        openser pops
>>           up an
>>           > error: ERROR: registrar:update_contacts: invalid cseq for aor
>>           <xxxx>. Has
>>           > anyone saw this before? I am using openser1.3.2.
>>
>>
>>           Hi joy,
>>
>>           no, there is no such a limitiation, we've more registered
>>        users.
>>           The invalid
>>           CSEQ error you see is not related to this observation. The
>>        error
>>           means that a
>>           device tried to do re-registration (same callid), but
>>        without properly
>>           increasing the Cseq number in the REGISTER request -
>>        RFC3261 says that
>>           requests from the same dialog (like REGISTER + re-REGISTER)
>>        must have
>>           increasing cseq.
>>
>>           What db_mode do you use in your usrloc? Do you see any other
>>           errors in the
>>           logs?
>>
>>           Cheers,
>>
>>
>>           Henning
>>
>>
>>
>>  ------------------------------------------------------------------------
>>
>>
>>
>>        _______________________________________________
>>        Kamailio (OpenSER) - Users mailing list
>>        Users at lists.kamailio.org <mailto:Users at lists.kamailio.org>
>>        http://lists.kamailio.org/cgi-bin/mailman/listinfo/users
>>        http://lists.openser-project.org/cgi-bin/mailman/listinfo/users
>>
>>
>>    --    Daniel-Constantin Mierla
>>    http://www.asipto.com
>>
>>
>> ------------------------------------------------------------------------
>>
>> _______________________________________________
>> Kamailio (OpenSER) - Users mailing list
>> Users at lists.kamailio.org
>> http://lists.kamailio.org/cgi-bin/mailman/listinfo/users
>> http://lists.openser-project.org/cgi-bin/mailman/listinfo/users
>>
>
> --
> Daniel-Constantin Mierla
> http://www.asipto.com
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.kamailio.org/pipermail/users/attachments/20090205/4aeca125/attachment.htm 