do you have proper indexes on columns?
Regards,
----- Original Message -----
From: "jyotiranjan panda" <[email protected]>
To: "Alejandro Guerrieri" <[email protected]>
Cc: <[email protected]>
Sent: 14 May 2009 10:49
Subject: Re: dlr-storage = mysql makes kannel slow ?
Hi Alejandro,
Let me explain my problem clearly.
When I am sending bulk MTs to smsc, kannel starts stores them in db after
getting the response of MTs and when dlr comes for respective MTs it
search
in the db and delete it from db.
And when there is data of 20k/30k in db I noticed bearerbox starts
decreasing the rate of sending messages to smsc. As the db size increases
the rate of sending messages to the smsc is decreases.
May be the problem arises due to the searching and deleting dlrs entry in
the db.
If I delete dlr entries from the db, bearerbox starts sending messages in
absolute manner.
I am using dlr-mask = 19.
Regards,
Jyoti Ranjan Panda
On Thu, May 14, 2009 at 3:00 PM, Alejandro Guerrieri <
[email protected]> wrote:
Well, dlr's should be deleted from the db when you receive the final
notification. Perhaps you should adjust the dlr-mask to not wait for
dlr's
you're not getting from the carrier.
Regards,
Alejandro
On Thu, May 14, 2009 at 10:50 AM, jyotiranjan panda
<[email protected]>wrote:
Hi,
I am using kannel-1.4.3 with dlr-storage = mysql.
I have noticed when I am using mysql storage, after 30,000 data in DB,
kannel starts processing message slowly. i.e it's just sending 2-3
msg/sec to upstream smsc, where as smsc TPS is 40.
At that time ,If I am deleting the data in DB,then it's sending in
normal
speed.
Please sugest how to improve the performance.
Regards
Jyoti Ranjan Panda
