Re: [asterisk-users] Using sqlite3 for CDR logging
Thanks for the feedback. I read someplace that the Berkeley DB was wicked fast and allowed for much higher concurrency. The only problem is that I have no idea how to implement it into Asterisk. Does anyone have any experience with something like this? Regards; John -Original Message- From: asterisk-users-boun...@lists.digium.com [mailto:asterisk-users-boun...@lists.digium.com] On Behalf Of Chris Bagnall Sent: Thursday, October 03, 2013 1:25 PM To: asterisk-users@lists.digium.com Subject: Re: [asterisk-users] Using sqlite3 for CDR logging On 3/10/13 5:52 pm, Tech Support wrote: I was thinking of using sqlite3 to log CDR's, thinking that would be faster than using MySQL. Has anyone ever benchmarked this to quantify just how much faster sqlite3 is? Are there any drawbacks to using it? Lack of multi-user concurrency is the big one. At the risk of encouraging database contests on the list, have you tried using PostgreSQL instead? It's a gross generalisation, but In my experience, PG handles writes better than MySQL, which in turn tends to handle reads a little faster than PG - assuming both are in 'out of the box' (i.e. unoptimised) conditions. If you wanted to stick with MySQL, you might want to have a go at optimising it - there are quite a few scripts knocking around the web which run a set of queries on your data and suggest optimisations to apply. And others have said, running the DB on a separate host is never a bad thing, and ideally on SSDs or RAM storage if you can. Spinning disks are often the bottleneck with large data sets. Kind regards, Chris -- This email is made from 100% recycled electrons -- _ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- New to Asterisk? Join us for a live introductory webinar every Thurs: http://www.asterisk.org/hello asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users -- _ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- New to Asterisk? Join us for a live introductory webinar every Thurs: http://www.asterisk.org/hello asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
[asterisk-users] Using sqlite3 for CDR logging
All; I am using Asterisk 1.8 and am running into some performance bottlenecks. Right now I am sending upwards of 700 concurrent faxes. I have no problem with that. The problems appear after the faxes complete. I was thinking of using sqlite3 to log CDR's, thinking that would be faster than using MySQL. Has anyone ever benchmarked this to quantify just how much faster sqlite3 is? Are there any drawbacks to using it? I would love to write to multiple sqlite3 databases, but that doesn't appear to be possible. Any insight at all on this would be greatly appreciated. Thanks; John. -- _ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- New to Asterisk? Join us for a live introductory webinar every Thurs: http://www.asterisk.org/hello asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] Using sqlite3 for CDR logging
faster than using MySQL. Has anyone ever benchmarked this to quantify Put Mysql on another machine and network the db service. -- _ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- New to Asterisk? Join us for a live introductory webinar every Thurs: http://www.asterisk.org/hello asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] Using sqlite3 for CDR logging
On 3/10/13 5:52 pm, Tech Support wrote: I was thinking of using sqlite3 to log CDR's, thinking that would be faster than using MySQL. Has anyone ever benchmarked this to quantify just how much faster sqlite3 is? Are there any drawbacks to using it? Lack of multi-user concurrency is the big one. At the risk of encouraging database contests on the list, have you tried using PostgreSQL instead? It's a gross generalisation, but In my experience, PG handles writes better than MySQL, which in turn tends to handle reads a little faster than PG - assuming both are in 'out of the box' (i.e. unoptimised) conditions. If you wanted to stick with MySQL, you might want to have a go at optimising it - there are quite a few scripts knocking around the web which run a set of queries on your data and suggest optimisations to apply. And others have said, running the DB on a separate host is never a bad thing, and ideally on SSDs or RAM storage if you can. Spinning disks are often the bottleneck with large data sets. Kind regards, Chris -- This email is made from 100% recycled electrons -- _ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- New to Asterisk? Join us for a live introductory webinar every Thurs: http://www.asterisk.org/hello asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
