Hi
I recently read the following in order to optimize OpenSER in handling TCP connections:
"First, the TCP supervisor process must be given an elevated priority level in order to prevent anomalous behavior due to the Linux scheduler."
First of all, as this is quite old paper (it refers to OpenSER 1.2), I'm wondering if such a tuning is still needed for Kamailio 1.5 branch ? If yes, how can I do this ?
Regards, Pascal
Hello,
On 07/07/2009 02:51 PM, Pascal Maugeri wrote:
where is this paper?
Thanks, Daniel
On Tue, Jul 7, 2009 at 2:58 PM, Daniel-Constantin Mierlamiconda@gmail.com wrote:
http://www.cs.rice.edu/CS/Architecture/docs/ram-ispass08.pdf (Section 4.3, page 6). -pascal
Thanks for the suggestion Jiri. So far I have been monitoring sr and I know that the TCP async implementation might resolve some problems we're facing with kamailio.
But I'm a bit conservative and I want to do several verifications of sr before doing the "switch". So for now we stick to kamailio.
Does this TCP supervisor process priority sounds familiar to you for tuning kamailio ?
Regards, Pascal
On Wed, Jul 8, 2009 at 12:25 AM, Jiri Kuthan jiri@iptel.org wrote:
On 07/08/2009 09:17 AM, Pascal Maugeri wrote:
this is good in any case, if you have high tcp load, as the dispatching of the connections is done with priority. Then are a bunch of worker processes dealing with tcp traffic.
Cheers, Daniel
On Wed, Jul 8, 2009 at 5:44 PM, Jiri Kuthan jiri@iptel.org wrote:
Sorry Jiri, but I disagree with you : if I understood well kamailio is still maintained as a product and will see future evolutions. And I'm pretty sure I will get some new issues to solve if we switch to sip-router. I need some time before doing this.
Cheers -pascal
Pascal Maugeri wrote:
Current Kamailio (1.5) is based on ser's old core. Next Kamailio release will be based on ser's new core (see sip-router.org). This new core has lots of TCP improvements.
Of course it makes sense to tune Kamailio 1.5 if you need TCP, but there wont be new features for the old core. New features will be added to sip-router core, which for sure has better TCP performance (see also the discussion on the sip-router list: http://lists.sip-router.org/pipermail/sr-dev/2009-July/002975.html)
regards Klaus
-
Daniel-Constantin Mierla -
Jiri Kuthan -
Klaus Darilion -
Pascal Maugeri