Hi, I intend to change the cdr_mysql-field "uniqueid", which seems not to be used so far, to an (not unique) indexed field and use it later for my own hints and infos. I don't have very much traffic so far, and I wonder, if there will appear problems when asterisk is under high load (100 simultanious calls) and the log table contains 1.000.000 log lines. This would mean, that asterisk would have to wait some time when writing a log line, because mysql has to update the index. Can anyone with some more experience predict, whether there will be problems cause to the indexed field? Your opinion is welcome! Roger.
Roger- Assuming that you have a fast machine, and a reasonably fast disk, I don't anticipate a problem at this call level. At one customer site, I have 5 systems, each running 120 lines with very high call volume - no problem with MySQL keeping up. This customer uses asterisk for IVR, not VoIP, and so has a higher rate of call setups than a typical VoIP setup would. I tend to clear out my DB's way before they reach 1,000,000 records however. You might consider doing what I do, and that's have a Perl process on each machine that transfers the DB records off to a database server on a very regular basis. I do it because of multiple machines - you might do it to maintain large numbers of records on-line. Cheers Scott Stingel Scott M. Stingel President, Emerging Voice Technology, Inc. Palo Alto California & London England www.evtmedia.com -----Original Message----- From: asterisk-users-admin@lists.digium.com [mailto:asterisk-users-admin@lists.digium.com] On Behalf Of Roger Schreiter Sent: Wednesday, May 12, 2004 7:13 AM To: asterisk-users@lists.digium.com Subject: [Asterisk-Users] cdr_mysql - would index slow down? Hi, I intend to change the cdr_mysql-field "uniqueid", which seems not to be used so far, to an (not unique) indexed field and use it later for my own hints and infos. I don't have very much traffic so far, and I wonder, if there will appear problems when asterisk is under high load (100 simultanious calls) and the log table contains 1.000.000 log lines. This would mean, that asterisk would have to wait some time when writing a log line, because mysql has to update the index. Can anyone with some more experience predict, whether there will be problems cause to the indexed field? Your opinion is welcome! Roger. _______________________________________________ Asterisk-Users mailing list Asterisk-Users@lists.digium.com http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
I have mySQL running on several servers where it is driving web-applications. One one site I track logins, ip-addresses and UAs, in addition to file downloads. The site is logging about 1,000,000 hits/month and the DB doesn't slow it down one but. mySQL has very good performance, as long as you plan your tables and indices well. On that note, you probably wouldn't re-use existing fields (whether they're used or not) but rather add new fields if needed. In order to keep insert-performance at peak, you may want to run table optimzation regularly. If size does become an issue, consider archiving old data -- you probably won't NEED 1,000,000 call records at your fingertips. Reality check: 100 simultaneous calls, 5 min average call, 6 days x 8 hours is less than 60K records per week, so 1M records would keep over four months of data. Even in that scenario, you only have about one insert every three seconds, and that shouldn't even cause a blip in your system load. Keep in mind that when asterisk is processing 100 simultaneous calls, you'll need a pretty beefy machine anyway, and if you're running a lot of queries against your CDR data, you may need to move the DB to a separate server. -----Original Message----- From: asterisk-users-admin@lists.digium.com [mailto:asterisk-users-admin@lists.digium.com] On Behalf Of Roger Schreiter Sent: Wednesday, May 12, 2004 9:13 AM To: asterisk-users@lists.digium.com Subject: [Asterisk-Users] cdr_mysql - would index slow down? Hi, I intend to change the cdr_mysql-field "uniqueid", which seems not to be used so far, to an (not unique) indexed field and use it later for my own hints and infos. I don't have very much traffic so far, and I wonder, if there will appear problems when asterisk is under high load (100 simultanious calls) and the log table contains 1.000.000 log lines. This would mean, that asterisk would have to wait some time when writing a log line, because mysql has to update the index. Can anyone with some more experience predict, whether there will be problems cause to the indexed field? Your opinion is welcome! Roger. _______________________________________________ Asterisk-Users mailing list Asterisk-Users@lists.digium.com http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Reasonably Related Threads
- cdr_mysql question: accountcode
- CDR_MYSQL 1.4 Database Structure
- Setting CDR(userfield) from Macro called from feature doesn't work with cdr_mysql
- shutting down a mysql server renders cdr_mysql dead and asterisk nolonger makes or receives calls
- Can't compile cdr_mysql