It goes without saying that you did not configure for debug ?
Aarno
On 15 Mar 2008, at 01:56, Dave Clarke wrote:
Thanks for this Alejandro
I'll look at trying the fake smsc. The carrier has given me a
throughput of 50, and advised that I split this across 2 binds,
which I have done,
Hi,
No not configured for debug. I think I may have isolated at least some of my
issues. I stopped using mysql for dlr processing, and chose internal
instead, and immediately have seen big jump in throughput. It looks as
though mysql has some problems on this server. Of course 'internal' dlr
Just a follow up to say I feel I've ruled out the carrier connection. I
routed everything through another bind, to a different carrier and still
found 150 messages took 82 seconds. I know this is something very basic, I'm
just not seeing it.
Dave
On 3/15/08, Alejandro Guerrieri [EMAIL PROTECTED]
may it be your internet connection?
what kind of connection do you have?
what available bandwidth?
is it used only by kannel, or also by other services?
On Sat, Mar 15, 2008 at 10:16 AM, Dave Clarke [EMAIL PROTECTED] wrote:
Just a follow up to say I feel I've ruled out the carrier connection.
Thanks Juan, but definitely not bandwidth issue. Got 3Mb both ways
uncontended, and it's working fine.
Dave
On 3/15/08, Juan Nin [EMAIL PROTECTED] wrote:
may it be your internet connection?
what kind of connection do you have?
what available bandwidth?
is it used only by kannel, or also
Are you 100% sure that the problem's not within your application?
I'd go nailing one possible point of failure at a time. If you can afford
making some tests offline, I'd connect the fake-smsc and simulate a few
hundred MO's and see how it perform. If you still have issues using
fake-smsc, then
Hi,
Having used kannel for a couple of years, I am now at a point where I need
to start ramping up my throughput, but I am finding that I can't sustain any
more than 2-3 messages a second through my 2x25 SMPP binds.
If I walk through my application:
- PHP/Apache/Postgresql application presents
Dave,
I can't make a 100% accurate diagnostic without further tests, but looks
like the bottleneck is on the links with the carrier.
You can try using the fake smsc module instead of your links, and queue a
fair amount of traffic. If the bottleneck is on those links, you'll get much
better
Thanks for this Alejandro
I'll look at trying the fake smsc. The carrier has given me a throughput of
50, and advised that I split this across 2 binds, which I have done, setting
the throughput figures at 25 and 25. I never see any throttling erors.
The reason I set the max-pending-submits to
Dave,
It certainly looks like a bottleneck on the link, but there are so many
variables involved that it's quit difficult to pinpoint the problem without
a lot of analysis and tests.
One more question: if you access the http interface on kannel, the store and
queued values gets higher and
10 matches
Mail list logo
