I do not want any fight here however here is my comments. If we use SQLBOX, below are the extra operations which happened.
1. Select from send_sms table 2. Delete from send_sms table 3. Insert into sent_sms table 4. Update sent_sms table once DLR received FOR EVERY SMS. As per my experience, if we connect any DB with kannel, it actually slow down the overall performance of kannel. In your case if you don't have MySQL in-between you might have achieved 500 TPS with same hardware. Regards Tapan Thapa On Wed, Apr 15, 2015 at 3:37 PM, spameden <spame...@gmail.com> wrote: > > > 2015-04-15 7:13 GMT+03:00 Tapan Kumar Thapa <tapan.thapa2...@gmail.com>: > >> If application is going to send huge number of messages via kannel than i >> think we should not configure kannel anyhow with MySQL (Or Any other >> database) as All databases actually slow the performance of kannel due to >> select/insert/update/delete operations. >> > > I do not agree with you on this. > > We've been using sqlbox for quite some time without any problems with huge > load some time ago (about 200-300 MT/sec real speed with multiple uplinks). > > We didn't log DLR reports tho, just updated MT records with relevant fresh > information from DLR. > > In most cases speed issue is SMSC issue not kannel at all if you do > everything right. > > >> >> We should make our own application in front of kannel for logging and any >> other operations. >> >> On Wed, Apr 15, 2015 at 3:54 AM, Alberto Mijares <amijar...@gmail.com> >> wrote: >> >>> Hi guys, >>> >>> I'd like to send bearerbox access logs directly to a MySQL table. I >>> think I could try >>> >>> group = core >>> ... >>> access-log = "/path/to/any/socket" >>> ... >>> >>> and have a script reading the socket, etc... >>> >>> Have anyone done this before? Any advise before I put my hands on >>> would be appretiated. >>> >>> Thanks in advance, >>> >>> >>> Alberto Mijares >>> >>> >> >
