On Sat, 2015-04-25 at 00:18, Daniel Camacho wrote:
I have worked with bothBut SQLBox was slower for me.If MySQL, MyISAM uses to
crash whe to much operation or a hardware failure.InnoDB is safest but slower
.
Your observation is true. Best solution for bulk messaging is custom
made
I have worked with bothBut SQLBox was slower for me.If MySQL, MyISAM uses to
crash whe to much operation or a hardware failure.InnoDB is safest but slower .
Http post was my solution.But What application is handling the requests and the
way it does, matters a lot.As light as possible the
SQLBOX is way faster for bulk traffic.
On Fri, Apr 24, 2015 at 1:48 AM, Rene Kluwen rene.klu...@chimit.nl wrote:
Unless your database is on another server.
Sqlbox keeps a tcp connection open to bearerbox.
If you use smsbox, you need to connect each time you send an sms.
I don’t have hard
Unless your database is on another server.
Sqlbox keeps a tcp connection open to bearerbox.
If you use smsbox, you need to connect each time you send an sms.
I don’t have hard figures though. It will be interesting to know them.
From: users [mailto:users-boun...@kannel.org] On Behalf Of
If you are sending One-To-Many kind of messages than you can also add
multiple mobile number in single HTTP get request.
On Tue, Apr 21, 2015 at 1:41 PM, Cliff Court cco...@telkomsa.net wrote:
Hi All
I have set up Kannel with bearerbox and smsbox, which is working and I am
writing dlr's to a
Hi All
I have set up Kannel with bearerbox and smsbox, which is working and I
am writing dlr's to a mysql db.
Currently I am submitting messages using a sendsms GET or xml-based
POST, as per the Kannel documentation. However, using individual http
GET or POSTs for each message is relatively
1.
I think Kannel does support Keep-Alive connections. Not sure about the server
side, but I think it does. Just make sure your client also supports it.
2.
Yes, probably SQL Box does insert 1,000,000 a lot faster than you can do by
http. Question is if your upstream providers handle such a
I'd say: with the propper DB and DBI (PostgrSQL + Perl DBI, ie), using
PREPARE and COMMIT, SQLBox is your best bet by far.
Regards,
Alberto Mijares
On Wed, Apr 22, 2015 at 12:50 AM, Makhanu Sinja jeysi...@gmail.com wrote:
Well last week The same issue was raised on another thread in this
Also while sqlbox is doing its operations with DB like select from
send_sms,submit to bearerbox and than inserting the same to sent_sms table
and doing delete from send_sms, it will add some time lag and will put load
on server too.
On Wed, Apr 22, 2015 at 11:10 AM, Tapan Kumar Thapa
Well last week The same issue was raised on another thread in this
mailing list. Let us consider the amount of time sqlbox has to do
database CRUD for 1M messages compared to using spool or files. Is
there anyone who has worked with both?
On 4/21/15, Rene Kluwen rene.klu...@chimit.nl wrote:
1.
My 2 cents:
Adding messages to send_sms table is not an issue. We can add messages to
send_sms table very quickly however once sqlbox is submitting those
messages to bearerbox, and if beaerebox is unable to submit the same to
upstream smsc at desired speed (because upstream smsc is not taking
11 matches
Mail list logo
