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-boun...@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> > 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.la...@cloudcall.com<mailto:phil.la...@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-boun...@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.la...@cloudcall.com<mailto:phil.la...@cloudcall.com>> wrote: What > rate of registrations do you have? > > > From: sr-users > [mailto:sr-users-boun...@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@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
