Thanks, that puts my performance worry to rest.

On Tue, Mar 3, 2015 at 10:48 PM, Alex Balashov <abalas...@evaristesys.com>
wrote:

> On 03/03/2015 12:08 PM, Jayanth Acharya wrote:
>
>  I am new to Kamilio (and SIP in general), but a quick research tells
>> that I've to configure Kamilio to run in the transaction stateful mode,
>> which in turn brings down it's performance. Is that correct ?
>>
>
> No, not really. :-)  This is true, strictly speaking, in a purely formal,
> computational sense, because maintaining state does entail more overhead.
> However, the advice to limit use of transaction-stateful mode for
> performance reasons really harks back to a different time in the evolution
> of computing hardware. With modern CPUs this difference is not significant,
> and Kamailio's internal architecture is still very performance-oriented.
>
> Moreover, I would say 90%+ of useful uses of Kamailio, such as this one,
> require transaction state. There's not much that can be done just by
> routing SIP messages ad hoc, based on their content alone. I think the only
> real use-case for stateless relay these days is a fire-and-forget load
> balancer.
>
> Opinions on this do vary, but regardless, you should not have any
> compunctions about using TM. If you look around on the web for example
> configs to do anything, virtually all of them use TM -- for a reason.
>
>
> -- Alex
>
> --
> Alex Balashov - Principal
> Evariste Systems LLC
> 235 E Ponce de Leon Ave
> Suite 106
> Decatur, GA 30030
> United States
>
> Tel: +1-678-954-0670
> Web: http://www.evaristesys.com/, http://www.alexbalashov.com/
>
> _______________________________________________
> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
> sr-users@lists.sip-router.org
> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
>
_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

Reply via email to