VoIP Mailing List Archives

[gmaruzz at celliax.org]

Maybe your load comes from disk access?

Try putting the sql and log directories on a ramdisk.

OTH,

-giovanni

On Tue, Aug 25, 2009 at 10:54 AM, Tihomir Culjaga<tculjaga@gmail.com> wrote:

[tculjaga at gmail.com]

Hey Giovanni,

thanks for the tip... indeed the db files were heavily used regardless if i started freeswitch with nosql option (freeswitch -nosql)... FS was not writing anything into that files ... instead it was just accessing it....
This behaviour leads to a waste of 40% CPU time... waiting for other processes (mainly disk access) to finish!!!

I moved freeswitch/db/ to a ramdisk and the performance got a boost to 140 CPS with a CPU load of 80%. I was keeping the machine for a while (20 - 30 minutes) on that rate when i sow CPU suddenly went to 100% and FS becoming irresponsive .


What can be wrong?
What are the limits in CPU usage (50%, 60%, 70%, 80%...) we should not cross?
What fine tuning do we need in order to asure a long high load run?



Also, I'm running 32-bit OS (debian 5) on a 64 bit CPU... does it have sense to move my OS to 64 bit? ... will FS gain more preformance ?... I mean will FS perofomr drastically better 20%+ ?


Tihomir.


On Tue, Aug 25, 2009 at 11:00 AM, Giovanni Maruzzelli <gmaruzz@celliax.org (gmaruzz@celliax.org)> wrote:

[tculjaga at gmail.com]

thanks for the feedback... this is something im going to do tomorrow...

what about other things?


On Tue, Aug 25, 2009 at 3:39 PM, Jay Binks <jaybinks@gmail.com (jaybinks@gmail.com)> wrote:

[jaybinks at gmail.com]

Everytime someone asks this , the resounding answer is use a 64bit os..


No question


Jay





On 25/08/2009, at 23:19, Tihomir Culjaga <tculjaga@gmail.com (tculjaga@gmail.com)> wrote:

[gmaruzz at celliax.org]

Definitely go for 64 bit OS.

If you want to be safe and sure, go for CentOS 5.2 64bit. Is the one
used both for development and for heavy duty production.

Also Ubuntu 8.04 is good.

Other versions/distros are less used by the community.

Adding RAM and CPUs helps to scale up.

-gm



Sincerely,

Giovanni Maruzzelli
Cell : +39-347-2665618




On Tue, Aug 25, 2009 at 3:19 PM, Tihomir Culjaga<tculjaga@gmail.com> wrote:

[gmaruzz at celliax.org]

is a heavely multithreaded software, it benefits from number of CPUs
(or cores), RAM, and heavy duty kernel features (found in 64bit
kernels)

put all accesses on ramdisk, leave out the modules you don't use...

experiment, test, and find the best for your specific application/workload

test not only with sipp, but with real load too (often they're very different)

-gm


On Tue, Aug 25, 2009 at 3:42 PM, Tihomir Culjaga<tculjaga@gmail.com> wrote:

[mike at jerris.com]

Actually in this case, we are bound to one thread in sofia.

Mike

On Aug 25, 2009, at 9:47 AM, Giovanni Maruzzelli wrote:

[msc at freeswitch.org]

[tculjaga at gmail.com]

Exactly... the scenario i use seems operating on a single thread... why is that ? can it be changed?

T.

On Tue, Aug 25, 2009 at 5:31 PM, Michael Jerris <mike@jerris.com (mike@jerris.com)> wrote:

[tculjaga at gmail.com]

well ... this is something we are going to change tomorrow.... of course will let you posted.

T.

On Tue, Aug 25, 2009 at 6:11 PM, Michael Collins <msc@freeswitch.org (msc@freeswitch.org)> wrote:

[anthony.minessale at g...]

You also should put your extension first in your dialplan ahead of the default extensions which match every call and do a lot of db access for
record keeping etc.

The single thread in sofia is part of their concurrency model.
The single thread acts as a scheduler and indicates to us that an invite is requested
we react to that and spawn a new thread for that call as soon as  the data is received.

like I said above you are probably hitting all the default stuff to save that last dialed number etc
that exists in the default config.

sigh, we go through this every new guy doing load testing.


On Tue, Aug 25, 2009 at 11:34 AM, Tihomir Culjaga <tculjaga@gmail.com (tculjaga@gmail.com)> wrote:

[mike at jerris.com]

This requires invasive changes in the sofia-sip stack to get thread-pooling working again. I am sure they would accept patches if you can provide some that fully address any issues that may come up from adding this such as race conditions.

Mike

On Aug 25, 2009, at 12:34 PM, Tihomir Culjaga wrote:

[tculjaga at gmail.com]

Of course i removed everytihng from teh dialplan except my extension

when exactly do you react and bring up a new thread ? ... is it on INVITE or on 1st 1xx response ?

i beleive i can have several lets call it SIP interfaces ... on different ports 5060, 5070, 5080 ... every interface will have it's own sip profile.

does it mean i will have one thread per profile?

T.


On Tue, Aug 25, 2009 at 7:10 PM, Anthony Minessale <anthony.minessale@gmail.com (anthony.minessale@gmail.com)> wrote:

[msc at freeswitch.org]

On Tue, Aug 25, 2009 at 10:31 AM, Tihomir Culjaga <tculjaga@gmail.com (tculjaga@gmail.com)> wrote:

[tculjaga at gmail.com]

Hi Giovanny,

thanks for your help,
everything that heavyly accesses the disk is on ramdisk now...
hopefully will get some real traffic pretty soon...


On Tue, Aug 25, 2009 at 3:47 PM, Giovanni Maruzzelli <gmaruzz@celliax.org (gmaruzz@celliax.org)> wrote: