24 Sep
2016
24 Sep
'16
9:39 p.m.
I have multiple Kamailio servers in an Active/Active scenario (the database
is a MySQL server) using db_mode 3. But when the number of clients goes up
writes on the location table become too much and it causes database
problems. I even put my location table on a separate SSD disk on the server
to separate it's IO but still at times I have problems. How can I move
location table into memory? Is this a good solution? What other options do
I have?
24 Sep
24 Sep
9:42 p.m.
What rate of registrations do you have?
From: sr-users [mailto:sr-users-bounces@lists.sip-router.org] On Behalf Of Gholamreza
Sabery
Sent: 24 September 2016 19:39
To: Kamailio (SER) - Users Mailing List <sr-users(a)lists.sip-router.org>
Subject: [SR-Users] Location Table In db_mode 3
I have multiple Kamailio servers in an Active/Active scenario (the database is a MySQL
server) using db_mode 3. But when the number of clients goes up writes on the location
table become too much and it causes database problems. I even put my location table on a
separate SSD disk on the server to separate it's IO but still at times I have
problems. How can I move location table into memory? Is this a good solution? What other
options do I have?
10:03 p.m.
On average I have about 2000 registrations per second and this
configuration does not work with this rate. Maximum number of registrations
that we can handle with db_mode 3 is 1000 per second.
On Sat, Sep 24, 2016 at 10:12 PM, Phil Lavin <phil.lavin(a)cloudcall.com>
wrote:
What rate of registrations do you have?
*From:* sr-users [mailto:sr-users-bounces@lists.sip-router.org] *On
Behalf Of *Gholamreza Sabery
*Sent:* 24 September 2016 19:39
*To:* Kamailio (SER) - Users Mailing List <sr-users(a)lists.sip-router.org>
*Subject:* [SR-Users] Location Table In db_mode 3
I have multiple Kamailio servers in an Active/Active scenario (the
database is a MySQL server) using db_mode 3. But when the number of clients
goes up writes on the location table become too much and it causes database
problems. I even put my location table on a separate SSD disk on the server
to separate it's IO but still at times I have problems. How can I move
location table into memory? Is this a good solution? What other options do
I have?
_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users(a)lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
10:20 p.m.
You could look at tweaking MySQL setting
innodb_flush_log_at_trx_commit<http://dev.mysql.com/doc/refman/5.7/en/in…
and setting its value to 0. It’ll make your database not ACID compliant, but I don’t see
that as being a major issue for transient data such as that stored in the Kamailio DB.
I’m not entirely convinced that changing it to a memory table will help as you are
presumably doing MySQL replication between your two Kamailio nodes. Memory tables don’t
replicate well.
From: sr-users [mailto:sr-users-bounces@lists.sip-router.org] On Behalf Of Gholamreza
Sabery
Sent: 24 September 2016 20:04
To: Kamailio (SER) - Users Mailing List <sr-users(a)lists.sip-router.org>
Subject: Re: [SR-Users] Location Table In db_mode 3
On average I have about 2000 registrations per second and this configuration does not work
with this rate. Maximum number of registrations that we can handle with db_mode 3 is 1000
per second.
On Sat, Sep 24, 2016 at 10:12 PM, Phil Lavin
<phil.lavin@cloudcall.com<mailto:phil.lavin@cloudcall.com>> wrote:
What rate of registrations do you have?
From: sr-users
[mailto:sr-users-bounces@lists.sip-router.org<mailto:sr-users-bounces@lists.sip-router.org>]
On Behalf Of Gholamreza Sabery
Sent: 24 September 2016 19:39
To: Kamailio (SER) - Users Mailing List
<sr-users@lists.sip-router.org<mailto:sr-users@lists.sip-router.org>>
Subject: [SR-Users] Location Table In db_mode 3
I have multiple Kamailio servers in an Active/Active scenario (the database is a MySQL
server) using db_mode 3. But when the number of clients goes up writes on the location
table become too much and it causes database problems. I even put my location table on a
separate SSD disk on the server to separate it's IO but still at times I have
problems. How can I move location table into memory? Is this a good solution? What other
options do I have?
_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org<mailto:sr-users@lists.sip-router.org>
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
10:24 p.m.
Also, what value do you have for MySQL parameter innodb_buffer_pool_size and how large is
your MySQL data directory at peak?
From: sr-users [mailto:sr-users-bounces@lists.sip-router.org] On Behalf Of Phil Lavin
Sent: 24 September 2016 20:20
To: Kamailio (SER) - Users Mailing List <sr-users(a)lists.sip-router.org>
Subject: Re: [SR-Users] Location Table In db_mode 3
You could look at tweaking MySQL setting
innodb_flush_log_at_trx_commit<http://dev.mysql.com/doc/refman/5.7/en/in…
and setting its value to 0. It’ll make your database not ACID compliant, but I don’t see
that as being a major issue for transient data such as that stored in the Kamailio DB.
I’m not entirely convinced that changing it to a memory table will help as you are
presumably doing MySQL replication between your two Kamailio nodes. Memory tables don’t
replicate well.
From: sr-users [mailto:sr-users-bounces@lists.sip-router.org] On Behalf Of Gholamreza
Sabery
Sent: 24 September 2016 20:04
To: Kamailio (SER) - Users Mailing List
<sr-users@lists.sip-router.org<mailto:sr-users@lists.sip-router.org>>
Subject: Re: [SR-Users] Location Table In db_mode 3
On average I have about 2000 registrations per second and this configuration does not work
with this rate. Maximum number of registrations that we can handle with db_mode 3 is 1000
per second.
On Sat, Sep 24, 2016 at 10:12 PM, Phil Lavin
<phil.lavin@cloudcall.com<mailto:phil.lavin@cloudcall.com>> wrote:
What rate of registrations do you have?
From: sr-users
[mailto:sr-users-bounces@lists.sip-router.org<mailto:sr-users-bounces@lists.sip-router.org>]
On Behalf Of Gholamreza Sabery
Sent: 24 September 2016 19:39
To: Kamailio (SER) - Users Mailing List
<sr-users@lists.sip-router.org<mailto:sr-users@lists.sip-router.org>>
Subject: [SR-Users] Location Table In db_mode 3
I have multiple Kamailio servers in an Active/Active scenario (the database is a MySQL
server) using db_mode 3. But when the number of clients goes up writes on the location
table become too much and it causes database problems. I even put my location table on a
separate SSD disk on the server to separate it's IO but still at times I have
problems. How can I move location table into memory? Is this a good solution? What other
options do I have?
_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org<mailto:sr-users@lists.sip-router.org>
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
10:25 p.m.
Thank you so much for your response. Well if putting the table into memory
is not a good option what is the best way to handle this situation?
On Sat, Sep 24, 2016 at 10:50 PM, Phil Lavin <phil.lavin(a)cloudcall.com>
wrote:
You could look at tweaking MySQL setting
innodb_flush_log_at_trx_commit
<http://dev.mysql.com/doc/refman/5.7/en/innodb-parameters.html#sysvar_innodb_flush_log_at_trx_commit>
and setting its value to *0*. It’ll make your database not ACID
compliant, but I don’t see that as being a major issue for transient data
such as that stored in the Kamailio DB.
I’m not entirely convinced that changing it to a memory table will help as
you are presumably doing MySQL replication between your two Kamailio nodes.
Memory tables don’t replicate well.
*From:* sr-users [mailto:sr-users-bounces@lists.sip-router.org] *On
Behalf Of *Gholamreza Sabery
*Sent:* 24 September 2016 20:04
*To:* Kamailio (SER) - Users Mailing List <sr-users(a)lists.sip-router.org>
*Subject:* Re: [SR-Users] Location Table In db_mode 3
On average I have about 2000 registrations per second and this
configuration does not work with this rate. Maximum number of registrations
that we can handle with db_mode 3 is 1000 per second.
On Sat, Sep 24, 2016 at 10:12 PM, Phil Lavin <phil.lavin(a)cloudcall.com>
wrote:
What rate of registrations do you have?
*From:* sr-users [mailto:sr-users-bounces@lists.sip-router.org] *On
Behalf Of *Gholamreza Sabery
*Sent:* 24 September 2016 19:39
*To:* Kamailio (SER) - Users Mailing List <sr-users(a)lists.sip-router.org>
*Subject:* [SR-Users] Location Table In db_mode 3
I have multiple Kamailio servers in an Active/Active scenario (the
database is a MySQL server) using db_mode 3. But when the number of clients
goes up writes on the location table become too much and it causes database
problems. I even put my location table on a separate SSD disk on the server
to separate it's IO but still at times I have problems. How can I move
location table into memory? Is this a good solution? What other options do
I have?
_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users(a)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(a)lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
10:37 p.m.
Did you have a look at
innodb_flush_log_at_trx_commit<http://dev.mysql.com/doc/refman/5.7/en/in…
Also, what value do you have for MySQL parameter innodb_buffer_pool_size and how large is
your MySQL data directory at peak?
From: sr-users [mailto:sr-users-bounces@lists.sip-router.org] On Behalf Of Gholamreza
Sabery
Sent: 24 September 2016 20:25
To: Kamailio (SER) - Users Mailing List <sr-users(a)lists.sip-router.org>
Subject: Re: [SR-Users] Location Table In db_mode 3
Thank you so much for your response. Well if putting the table into memory is not a good
option what is the best way to handle this situation?
On Sat, Sep 24, 2016 at 10:50 PM, Phil Lavin
<phil.lavin@cloudcall.com<mailto:phil.lavin@cloudcall.com>> wrote:
You could look at tweaking MySQL setting
innodb_flush_log_at_trx_commit<http://dev.mysql.com/doc/refman/5.7/en/in…
and setting its value to 0. It’ll make your database not ACID compliant, but I don’t see
that as being a major issue for transient data such as that stored in the Kamailio DB.
I’m not entirely convinced that changing it to a memory table will help as you are
presumably doing MySQL replication between your two Kamailio nodes. Memory tables don’t
replicate well.
From: sr-users
[mailto:sr-users-bounces@lists.sip-router.org<mailto:sr-users-bounces@lists.sip-router.org>]
On Behalf Of Gholamreza Sabery
Sent: 24 September 2016 20:04
To: Kamailio (SER) - Users Mailing List
<sr-users@lists.sip-router.org<mailto:sr-users@lists.sip-router.org>>
Subject: Re: [SR-Users] Location Table In db_mode 3
On average I have about 2000 registrations per second and this configuration does not work
with this rate. Maximum number of registrations that we can handle with db_mode 3 is 1000
per second.
On Sat, Sep 24, 2016 at 10:12 PM, Phil Lavin
<phil.lavin@cloudcall.com<mailto:phil.lavin@cloudcall.com>> wrote:
What rate of registrations do you have?
From: sr-users
[mailto:sr-users-bounces@lists.sip-router.org<mailto:sr-users-bounces@lists.sip-router.org>]
On Behalf Of Gholamreza Sabery
Sent: 24 September 2016 19:39
To: Kamailio (SER) - Users Mailing List
<sr-users@lists.sip-router.org<mailto:sr-users@lists.sip-router.org>>
Subject: [SR-Users] Location Table In db_mode 3
I have multiple Kamailio servers in an Active/Active scenario (the database is a MySQL
server) using db_mode 3. But when the number of clients goes up writes on the location
table become too much and it causes database problems. I even put my location table on a
separate SSD disk on the server to separate it's IO but still at times I have
problems. How can I move location table into memory? Is this a good solution? What other
options do I have?
_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org<mailto: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<mailto:sr-users@lists.sip-router.org>
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
11:37 p.m.
I'd avoid slow innodb engine for "temporary" frequently changing tables like
location. Use MyISAM engine instead for the table.
On Saturday 24 September 2016 19:37:22 Phil Lavin wrote:
Did you have a look at
innodb_flush_log_at_trx_commit<http://dev.mysql.com/doc/refman/5.7/en/in…
b-parameters.html#sysvar_innodb_flush_log_at_trx_commit>?
Also, what value do you have for MySQL parameter
innodb_buffer_pool_size and
how large is your MySQL data directory at peak?
From: sr-users [mailto:sr-users-bounces@lists.sip-router.org] On Behalf Of
Gholamreza Sabery
Sent: 24 September 2016 20:25
To: Kamailio (SER) - Users Mailing List
<sr-users(a)lists.sip-router.org>
Subject: Re: [SR-Users] Location Table In db_mode 3
Thank you so much for your response. Well if putting the table into memory
is not a good option what is the best way to handle this situation?
On Sat, Sep 24, 2016 at 10:50 PM, Phil Lavin
<phil.lavin@cloudcall.com<mailto:phil.lavin@cloudcall.com>> wrote:
You
could look at tweaking MySQL setting
innodb_flush_log_at_trx_commit<http://dev.mysql.com/doc/refman/5.7/en/in…
b-parameters.html#sysvar_innodb_flush_log_at_trx_commit> and setting its
value to 0. It’ll make your database not ACID compliant, but I don’t see
that as being a major issue for transient data such as that stored in the
Kamailio DB.
I’m not entirely convinced that changing it to a memory table will help as
you are presumably doing MySQL replication between your two Kamailio nodes.
Memory tables don’t replicate well.
From: sr-users
[mailto:sr-users-bounces@lists.sip-router.org<mailto:sr-users-bounces@lists
.sip-router.org>] On Behalf Of Gholamreza Sabery
Sent: 24 September 2016
20:04
To: Kamailio (SER) - Users Mailing List
<sr-users@lists.sip-router.org<mailto:sr-users@lists.sip-router.org>>
Subject: Re: [SR-Users] Location Table In db_mode 3
On average I have about 2000 registrations per second and this configuration
does not work with this rate. Maximum number of registrations that we can
handle with db_mode 3 is 1000 per second.
On Sat, Sep 24, 2016 at 10:12 PM, Phil Lavin
<phil.lavin@cloudcall.com<mailto:phil.lavin@cloudcall.com>> wrote:
What
> rate of registrations do you have?
>
From: sr-users
[mailto:sr-users-bounces@lists.sip-router.org<mailto:sr-users-bounces@lists
.sip-router.org>] On Behalf Of Gholamreza Sabery
Sent: 24 September 2016
19:39
To: Kamailio (SER) - Users Mailing List
<sr-users@lists.sip-router.org<mailto:sr-users@lists.sip-router.org>>
Subject: [SR-Users] Location Table In db_mode 3
I have multiple Kamailio servers in an Active/Active scenario (the database
is a MySQL server) using db_mode 3. But when the number of clients goes up
writes on the location table become too much and it causes database
problems. I even put my location table on a separate SSD disk on the server
to separate it's IO but still at times I have problems. How can I move
location table into memory? Is this a good solution? What other options do
I have?
_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org<mailto: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<mailto:sr-users@lists.sip-router.org>
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
25 Sep
25 Sep
11:16 a.m.
Thank you very much for your responses. My innodb_buffer_pool_size = 16GB
and data files are about 92 MB and
innodb_flush_log_at_trx_commit= 1
On Sun, Sep 25, 2016 at 12:07 AM, Sergey Okhapkin <sos(a)sokhapkin.dyndns.org>
wrote:
I'd avoid slow innodb engine for
"temporary" frequently changing tables
like
location. Use MyISAM engine instead for the table.
On Saturday 24 September 2016 19:37:22 Phil Lavin wrote:
Did you have a look at
innodb_flush_log_at_trx_commit<http://dev.mysql.com/
doc/refman/5.7/en/innod
b-parameters.html#sysvar_innodb_flush_log_at_trx_commit>?
Also, what value do you have for MySQL parameter
innodb_buffer_pool_size
and
how large is your MySQL data directory at peak?
From: sr-users [mailto:sr-users-bounces@lists.sip-router.org] On Behalf
Of
Gholamreza Sabery
Sent: 24 September 2016
20:25
To: Kamailio (SER) - Users Mailing List
<sr-users(a)lists.sip-router.org>
Subject: Re: [SR-Users] Location Table In db_mode 3
Thank you so much for your response. Well if putting the table into
memory
is not a good option what is the best way to
handle this situation?
On Sat, Sep 24, 2016 at 10:50 PM, Phil Lavin
<phil.lavin@cloudcall.com<mailto:phil.lavin@cloudcall.com>> wrote:
You
could look at tweaking MySQL setting
innodb_flush_log_at_trx_commit<http://dev.mysql.com/
doc/refman/5.7/en/innod
b-parameters.html#sysvar_innodb_flush_log_at_trx_commit> and setting its
value to 0. It’ll make your database not ACID compliant, but I don’t see
that as being a major issue for transient data such as that stored in the
Kamailio DB.
I’m not entirely convinced that changing it to a memory table will help
as
you are presumably doing MySQL replication
between your two Kamailio
nodes.
Memory tables don’t replicate well.
From: sr-users
[mailto:sr-users-bounces@lists.sip-router.org<mailto:sr
-users-bounces@lists
.sip-router.org>] On Behalf Of Gholamreza
Sabery
Sent: 24 September 2016
20:04
To: Kamailio (SER) - Users Mailing List
<sr-users@lists.sip-router.org<mailto:sr-users@lists.sip-router.org>>
Subject: Re: [SR-Users] Location Table In db_mode 3
On average I have about 2000 registrations per second and this
configuration
does not work with this rate. Maximum number of
registrations that we can
handle with db_mode 3 is 1000 per second.
On Sat, Sep 24, 2016 at 10:12 PM, Phil Lavin
<phil.lavin@cloudcall.com<mailto:phil.lavin@cloudcall.com>> wrote:
What
> rate of registrations do you have?
>
From: sr-users
[mailto:sr-users-bounces@lists.sip-router.org<mailto:sr
-users-bounces@lists
.sip-router.org>] On Behalf Of Gholamreza
Sabery
Sent: 24 September 2016
19:39
To: Kamailio (SER) - Users Mailing List
<sr-users@lists.sip-router.org<mailto:sr-users@lists.sip-router.org>>
Subject: [SR-Users] Location Table In db_mode 3
I have multiple Kamailio servers in an Active/Active scenario (the
database
is a MySQL server) using db_mode 3. But when the
number of clients goes
up
writes on the location table become too much and
it causes database
problems. I even put my location table on a separate SSD disk on the
server
to separate it's IO but still at times I have
problems. How can I move
location table into memory? Is this a good solution? What other options
do
I have?
_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org<mailto: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<mailto: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(a)lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
11:49 a.m.
Setting it to 0 will give you significantly enhanced performance. It will only write data
to disk every second.
From: sr-users [mailto:sr-users-bounces@lists.sip-router.org] On Behalf Of Gholamreza
Sabery
Sent: 25 September 2016 09:16
To: Kamailio (SER) - Users Mailing List <sr-users(a)lists.sip-router.org>
Subject: Re: [SR-Users] Location Table In db_mode 3
Thank you very much for your responses. My innodb_buffer_pool_size = 16GB and data files
are about 92 MB and
innodb_flush_log_at_trx_commit= 1
On Sun, Sep 25, 2016 at 12:07 AM, Sergey Okhapkin
<sos@sokhapkin.dyndns.org<mailto:sos@sokhapkin.dyndns.org>> wrote:
I'd avoid slow innodb engine for "temporary" frequently changing tables
like
location. Use MyISAM engine instead for the table.
On Saturday 24 September 2016 19:37:22 Phil Lavin wrote:
Did you have a look at
innodb_flush_log_at_trx_commit<http://dev.mysql.com/doc/refman/5.7/en/in…
b-parameters.html#sysvar_innodb_flush_log_at_trx_commit>?
Also, what value do you have for MySQL parameter
innodb_buffer_pool_size and
how large is your MySQL data directory at peak?
From: sr-users
[mailto:sr-users-bounces@lists.sip-router.org<mailto:sr-users-bounces@lists.sip-router.org>]
On Behalf Of
Gholamreza Sabery
Sent: 24 September 2016 20:25
To: Kamailio (SER) - Users Mailing List
<sr-users@lists.sip-router.org<mailto:sr-users@lists.sip-router.org>>
Subject: Re: [SR-Users] Location Table In db_mode 3
Thank you so much for your response. Well if putting the table into memory
is not a good option what is the best way to handle this situation?
On Sat, Sep 24, 2016 at 10:50 PM, Phil Lavin
<phil.lavin@cloudcall.com<mailto:phil.lavin@cloudcall.com><mailto:phil.lavin@cloudcall.com<mailto:phil.lavin@cloudcall.com>>>
wrote:
You
could look at tweaking MySQL setting
innodb_flush_log_at_trx_commit<http://dev.mysql.com/doc/refman/5.7/en/in…
b-parameters.html#sysvar_innodb_flush_log_at_trx_commit> and setting its
value to 0. It’ll make your database not ACID compliant, but I don’t see
that as being a major issue for transient data such as that stored in the
Kamailio DB.
I’m not entirely convinced that changing it to a memory table will help as
you are presumably doing MySQL replication between your two Kamailio nodes.
Memory tables don’t replicate well.
From: sr-users
[mailto:sr-users-bounces@lists.sip-router.org<mailto:sr-users-bounces@lists.sip-router.org><mailto:sr-users-bounces@lists<mailto:sr-users-bounces@lists>
.sip-router.org<http://sip-router.org>>] On Behalf Of Gholamreza Sabery
Sent: 24 September 2016
20:04
To: Kamailio (SER) - Users Mailing List
<sr-users@lists.sip-router.org<mailto:sr-users@lists.sip-router.org><mailto:sr-users@lists.sip-router.org<mailto:sr-users@lists.sip-router.org>>>
Subject: Re: [SR-Users] Location Table In db_mode 3
On average I have about 2000 registrations per second and this configuration
does not work with this rate. Maximum number of registrations that we can
handle with db_mode 3 is 1000 per second.
On Sat, Sep 24, 2016 at 10:12 PM, Phil Lavin
<phil.lavin@cloudcall.com<mailto:phil.lavin@cloudcall.com><mailto:phil.lavin@cloudcall.com<mailto:phil.lavin@cloudcall.com>>>
wrote:
What
> rate of registrations do you have?
>
From: sr-users
[mailto:sr-users-bounces@lists.sip-router.org<mailto:sr-users-bounces@lists.sip-router.org><mailto:sr-users-bounces@lists<mailto:sr-users-bounces@lists>
.sip-router.org<http://sip-router.org>>] On Behalf Of Gholamreza Sabery
Sent: 24 September 2016
19:39
To: Kamailio (SER) - Users Mailing List
<sr-users@lists.sip-router.org<mailto:sr-users@lists.sip-router.org><mailto:sr-users@lists.sip-router.org<mailto:sr-users@lists.sip-router.org>>>
Subject: [SR-Users] Location Table In db_mode 3
I have multiple Kamailio servers in an Active/Active scenario (the database
is a MySQL server) using db_mode 3. But when the number of clients goes up
writes on the location table become too much and it causes database
problems. I even put my location table on a separate SSD disk on the server
to separate it's IO but still at times I have problems. How can I move
location table into memory? Is this a good solution? What other options do
I have?
_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org<mailto:sr-users@lists.sip-router.org><mailto:sr-users@lists.sip-router.org<mailto: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<mailto:sr-users@lists.sip-router.org><mailto:sr-users@lists.sip-router.org<mailto: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<mailto:sr-users@lists.sip-router.org>
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
12:24 p.m.
Thank you so much. I will try it; but it seems that this option affects the
whole database. I want something fine grained that can be applied to
specific tables. Or other solutions. It seems that Kmailio's session
management in a shared database mode (in a Kamailio cluster) is not good
enough for high performance clusters. Are there other ways to share session
information in Kamailio clusters so we can know where a user is registered?
On Sun, Sep 25, 2016 at 12:19 PM, Phil Lavin <phil.lavin(a)cloudcall.com>
wrote:
Setting it to 0 will give you significantly enhanced
performance. It will
only write data to disk every second.
*From:* sr-users [mailto:sr-users-bounces@lists.sip-router.org] *On
Behalf Of *Gholamreza Sabery
*Sent:* 25 September 2016 09:16
*To:* Kamailio (SER) - Users Mailing List <sr-users(a)lists.sip-router.org>
*Subject:* Re: [SR-Users] Location Table In db_mode 3
Thank you very much for your responses. My innodb_buffer_pool_size = 16GB
and data files are about 92 MB and
innodb_flush_log_at_trx_commit= 1
On Sun, Sep 25, 2016 at 12:07 AM, Sergey Okhapkin <
sos(a)sokhapkin.dyndns.org> wrote:
I'd avoid slow innodb engine for "temporary" frequently changing tables
like
location. Use MyISAM engine instead for the table.
On Saturday 24 September 2016 19:37:22 Phil Lavin wrote:
Did you have a look at
innodb_flush_log_at_trx_commit<http://dev.mysql.com/
doc/refman/5.7/en/innod
b-parameters.html#sysvar_innodb_flush_log_at_trx_commit>?
Also, what value do you have for MySQL parameter
innodb_buffer_pool_size
and
how large is your MySQL data directory at peak?
From: sr-users [mailto:sr-users-bounces@lists.sip-router.org] On Behalf
Of
Gholamreza Sabery
Sent: 24 September 2016
20:25
To: Kamailio (SER) - Users Mailing List
<sr-users(a)lists.sip-router.org>
Subject: Re: [SR-Users] Location Table In db_mode 3
Thank you so much for your response. Well if putting the table into
memory
is not a good option what is the best way to
handle this situation?
On Sat, Sep 24, 2016 at 10:50 PM, Phil Lavin
<phil.lavin@cloudcall.com<mailto:phil.lavin@cloudcall.com>> wrote:
You
could look at tweaking MySQL setting
innodb_flush_log_at_trx_commit<http://dev.mysql.com/
doc/refman/5.7/en/innod
b-parameters.html#sysvar_innodb_flush_log_at_trx_commit> and setting its
value to 0. It’ll make your database not ACID compliant, but I don’t see
that as being a major issue for transient data such as that stored in the
Kamailio DB.
I’m not entirely convinced that changing it to a memory table will help
as
you are presumably doing MySQL replication
between your two Kamailio
nodes.
Memory tables don’t replicate well.
From: sr-users
[mailto:sr-users-bounces@lists.sip-router.org<mailto:sr
-users-bounces@lists
.sip-router.org>] On Behalf Of Gholamreza
Sabery
Sent: 24 September 2016
20:04
To: Kamailio (SER) - Users Mailing List
<sr-users@lists.sip-router.org<mailto:sr-users@lists.sip-router.org>>
Subject: Re: [SR-Users] Location Table In db_mode 3
On average I have about 2000 registrations per second and this
configuration
does not work with this rate. Maximum number of
registrations that we can
handle with db_mode 3 is 1000 per second.
On Sat, Sep 24, 2016 at 10:12 PM, Phil Lavin
<phil.lavin@cloudcall.com<mailto:phil.lavin@cloudcall.com>> wrote:
What
> rate of registrations do you have?
>
From: sr-users
[mailto:sr-users-bounces@lists.sip-router.org<mailto:sr
-users-bounces@lists
.sip-router.org>] On Behalf Of Gholamreza
Sabery
Sent: 24 September 2016
19:39
To: Kamailio (SER) - Users Mailing List
<sr-users@lists.sip-router.org<mailto:sr-users@lists.sip-router.org>>
Subject: [SR-Users] Location Table In db_mode 3
I have multiple Kamailio servers in an Active/Active scenario (the
database
is a MySQL server) using db_mode 3. But when the
number of clients goes
up
writes on the location table become too much and
it causes database
problems. I even put my location table on a separate SSD disk on the
server
to separate it's IO but still at times I have
problems. How can I move
location table into memory? Is this a good solution? What other options
do
I have?
_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org<mailto: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<mailto:sr-users@lists.sip-router.org>
_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users(a)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(a)lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
12:41 p.m.
That is the case, however I don't believe this is a problem unless you have other
databases on the same server that must be ACID compliant on the same server.
Kamailio's DB data is mostly transient and that which isn't is not written at high
volume (e.g. address table).
-----Original Message-----
From: sr-users [mailto:sr-users-bounces@lists.sip-router.org] On Behalf Of Juha Heinanen
Sent: 25 September 2016 10:35
To: Kamailio (SER) - Users Mailing List <sr-users(a)lists.sip-router.org>
Subject: Re: [SR-Users] Location Table In db_mode 3
Gholamreza Sabery writes:
Thank you so much. I will try it; but it seems that
this option
affects the whole database.
I think it applies to the whole mysql server, i.e., to all of its databases.
-- Juha
_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users(a)lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
2987
days inactive
2988
days old
12 comments
4 participants
participants (4)
-
Gholamreza Sabery -
Juha Heinanen -
Phil Lavin -
Sergey Okhapkin