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:
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
where is this paper?
Thanks, Daniel
(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
Kamailio (OpenSER) - Users mailing list Users@lists.kamailio.org http://lists.kamailio.org/cgi-bin/mailman/listinfo/users http://lists.openser-project.org/cgi-bin/mailman/listinfo/users
On Tue, Jul 7, 2009 at 2:58 PM, Daniel-Constantin Mierlamiconda@gmail.com wrote:
Hello,
On 07/07/2009 02:51 PM, Pascal Maugeri wrote:
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
where is this paper?
http://www.cs.rice.edu/CS/Architecture/docs/ram-ispass08.pdf (Section 4.3, page 6). -pascal
Thanks, Daniel
(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
Kamailio (OpenSER) - Users mailing list Users@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/
if you are concerned about TCP performance (Which may be a justified concern -- from any possible viewpoint TCP is not easy for SIP), I suggest you consider the sip-router core. There has been (and I think still will be) tremendous effort put in it.
-jiri
Pascal Maugeri wrote:
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
Kamailio (OpenSER) - Users mailing list Users@lists.kamailio.org http://lists.kamailio.org/cgi-bin/mailman/listinfo/users http://lists.openser-project.org/cgi-bin/mailman/listinfo/users
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:
if you are concerned about TCP performance (Which may be a justified concern -- from any possible viewpoint TCP is not easy for SIP), I suggest you consider the sip-router core. There has been (and I think still will be) tremendous effort put in it.
-jiri
Pascal Maugeri wrote:
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
Kamailio (OpenSER) - Users mailing list Users@lists.kamailio.org http://lists.kamailio.org/cgi-bin/mailman/listinfo/users http://lists.openser-project.org/cgi-bin/mailman/listinfo/users
On 07/08/2009 09:17 AM, Pascal Maugeri wrote:
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 ?
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
Regards, Pascal
On Wed, Jul 8, 2009 at 12:25 AM, Jiri Kuthan <jiri@iptel.org mailto:jiri@iptel.org> wrote:
if you are concerned about TCP performance (Which may be a justified concern -- from any possible viewpoint TCP is not easy for SIP), I suggest you consider the sip-router core. There has been (and I think still will be) tremendous effort put in it. -jiri Pascal Maugeri wrote: 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 _______________________________________________ Kamailio (OpenSER) - Users mailing list Users@lists.kamailio.org <mailto:Users@lists.kamailio.org> http://lists.kamailio.org/cgi-bin/mailman/listinfo/users http://lists.openser-project.org/cgi-bin/mailman/listinfo/users
Kamailio (OpenSER) - Users mailing list Users@lists.kamailio.org http://lists.kamailio.org/cgi-bin/mailman/listinfo/users http://lists.openser-project.org/cgi-bin/mailman/listinfo/users
On Wed, Jul 8, 2009 at 11:30 AM, Daniel-Constantin Mierla <miconda@gmail.com
wrote:
On 07/08/2009 09:17 AM, Pascal Maugeri wrote:
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 ?
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.
Could you point me to the right documentation in order to achieve this ?
Thanks in advance -pascal
Cheers, Daniel
Regards, Pascal
On Wed, Jul 8, 2009 at 12:25 AM, Jiri Kuthan <jiri@iptel.org mailto: jiri@iptel.org> wrote:
if you are concerned about TCP performance (Which may be a justified concern -- from any possible viewpoint TCP is not easy for SIP), I suggest you consider the sip-router core. There has been (and I think still will be) tremendous effort put in it.
-jiri
Pascal Maugeri wrote:
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 _______________________________________________ Kamailio (OpenSER) - Users mailing list Users@lists.kamailio.org <mailto:Users@lists.kamailio.org> http://lists.kamailio.org/cgi-bin/mailman/listinfo/users http://lists.openser-project.org/cgi-bin/mailman/listinfo/users
Kamailio (OpenSER) - Users mailing list Users@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/
Pascal Maugeri wrote:
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 ?
not really -- I sort of think that studying tuning of something what is overdue for an update may cost you lot of time and bring less results.
-jiri
Regards, Pascal
On Wed, Jul 8, 2009 at 12:25 AM, Jiri Kuthan <jiri@iptel.org mailto:jiri@iptel.org> wrote:
if you are concerned about TCP performance (Which may be a justified concern -- from any possible viewpoint TCP is not easy for SIP), I suggest you consider the sip-router core. There has been (and I think still will be) tremendous effort put in it. -jiri Pascal Maugeri wrote: 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 _______________________________________________ Kamailio (OpenSER) - Users mailing list Users@lists.kamailio.org <mailto:Users@lists.kamailio.org> http://lists.kamailio.org/cgi-bin/mailman/listinfo/users http://lists.openser-project.org/cgi-bin/mailman/listinfo/users
On Wed, Jul 8, 2009 at 5:44 PM, Jiri Kuthan jiri@iptel.org wrote:
Pascal Maugeri wrote:
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 ?
not really -- I sort of think that studying tuning of something what is overdue for an update may cost you lot of time and bring less results.
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
-jiri
Regards, Pascal
On Wed, Jul 8, 2009 at 12:25 AM, Jiri Kuthan <jiri@iptel.org mailto: jiri@iptel.org> wrote:
if you are concerned about TCP performance (Which may be a justified concern -- from any possible viewpoint TCP is not easy for SIP), I suggest you consider the sip-router core. There has been (and I think still will be) tremendous effort put in it.
-jiri
Pascal Maugeri wrote:
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 OpenSER1.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 _______________________________________________ Kamailio (OpenSER) - Users mailing list Users@lists.kamailio.org <mailto:Users@lists.kamailio.org> http://lists.kamailio.org/cgi-bin/mailman/listinfo/users http://lists.openser-project.org/cgi-bin/mailman/listinfo/users
Pascal Maugeri wrote:
On Wed, Jul 8, 2009 at 5:44 PM, Jiri Kuthan <jiri@iptel.org mailto:jiri@iptel.org> wrote:
Pascal Maugeri wrote: 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 ? not really -- I sort of think that studying tuning of something what is overdue for an update may cost you lot of time and bring less results.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.
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