I checked mysql documentation for using DELAYED. It seems like it is handling the speed on the submitting side of SQLBOX (e.g. submitting data into SQLBOX). While I am trying to make SQLBOX push the messages more quickly to bearerbox. Would it serve the same purpose that I am pursuing?
I am using MySQL and the RAM of machine is 16GB. Can the size of database be a factor? Currently sent_sms contains over 10 million entries... Any other tips? Should I use a separate database machine? It makes less logic because I still have over 50% CPU idle time and at least 13GB of RAM free at even load times. On Mon, Apr 25, 2011 at 7:37 PM, Rene Kluwen <[email protected]> wrote: > If you think that the sql engine is the problem. And you are using MySQL… > then try to add the “DELAYED” keyword in the SQLBOX_MYSQL_INSERT_QUERY in > gw/sqlbox_mysql.h source file. > > See the mysql documentation. If it helps: Let us know! > > > > == Rene > > > > *From:* [email protected] [mailto:[email protected]] *On > Behalf Of *Juan Nin > *Sent:* Monday, 25 April, 2011 03:16 > *To:* users > *Subject:* Re: Kannel SMS sending speed > > > > What DB engine are you using, and what table type? > > > > On Sun, Apr 24, 2011 at 6:01 AM, [email protected] <[email protected]> wrote: > > Hi, > > > > My kannel speed of sending SMS is varying randomly. Over the past 12 > months, I have observed very carefully about the factors affecting the > speed. Let me share the important points with you: > > > > - I have 20 different SMSC connections with one single operator > > - All connections have individual speed = 20 message/sec > > - My kannel config is following: BBOX <-> SQLBOX <-> SMSBOX <-> Application > > - Over different times, SMS bulk gets different overall processing speed. I > checked network conditions as well as SMSC state, both have no issues. > > - Now for the same campaigns, I observe following difference in kannel > monitoring window: > > > > When I am getting perfect speed, following line carries a lot of queued > messages in SENT ONLY (kannel monitoring window): > > > > SMS: received 1427 (0 queued), sent 71000 (308 queued), store size -1 > > SMS: inbound (2.50,0.59,0.80) msg/sec, outbound (132.31,24.39,30.65) > msg/sec > > > > Also in individual SMSC connection threads, I see SMS queued on every > thread: > > > > *90101*[90101] SMPP:x.x.x.x:y/y:90101:90101 (online 3866s, rcvd: sms 40 > / dlr 0, sent: sms 1874 / dlr 0, failed 0, queued 1200 msgs) > *90102*[90102] SMPP:x.x.x.x:y/y:90102:90102 (online 3866s, rcvd: sms 35 > / dlr 0, sent: sms 1943 / dlr 0, failed 0, queued 1148 msgs) > *90103*[90103] SMPP:x.x.x.x:y/y:90103:90103 (online 3866s, rcvd: sms 28 > / dlr 0, sent: sms 1936 / dlr 0, failed 0, queued 1320 msgs) > > > > ---------------------------------------------- > > On the contrary, when I am not getting good speed, following observations I > can make on same window: > > > > SMS: received 149 (0 queued), sent 3702 (0 queued), store size -1 > SMS: inbound (0.10,0.02,0.04) msg/sec, outbound (17.27,17.67,19.06) > msg/sec > > > > *90101*[90101] SMPP:x.x.x.x:y/y:90101:90101 (online 4229s, rcvd: sms 0 > / dlr 0, sent: sms 2050 / dlr 0, failed 0, queued 0 msgs) > *90102*[90102] SMPP:x.x.x.x:y/y:90102:90102 (online 4229s, rcvd: sms 0 > / dlr 0, sent: sms 2083 / dlr 0, failed 0, queued 0 msgs) > *90103*[90103] SMPP:x.x.x.x:y/y:90103:90103 (online 4229s, rcvd: sms 0 > / dlr 0, sent: sms 2112 / dlr 0, failed 0, queued 0 msgs) > > > > ----------------------------------------------- > > > > It seems that SQLBOX does not push the SMS to bearerbox with constant > speed. Although more speed is available with SMSC connections, still I dont > see kannel achieving high speed unless I see queued messages in SMSC > connections. > > > > Can someone support my hypothesis? How to speed up SQLBOX's pushing of SMS > to BBOX? > > > > Regards, > > Hamza > > > > > > >
