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.
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> wrote:
Actually in this case, we are bound to one thread in sofia.
Mike
On Aug 25, 2009, at 9:47 AM, Giovanni Maruzzelli wrote:
> 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
>
_______________________________________________
FreeSWITCH-users mailing list
FreeSWITCH-users@lists.freeswitch.org
http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
http://www.freeswitch.org
_______________________________________________
FreeSWITCH-users mailing list
FreeSWITCH-users@lists.freeswitch.org
http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
http://www.freeswitch.org