Hi Aarno.
I think this problem occurs as the bearerbox can't send messages as fast
as they are delivered (probably due to a large burst and then sustained
high load). I see messages queued on the module's queue, and then it
slows doesn the module more, so it can handle less messages (while high
load continues) and so the queue grows longer.
Possible solution would be to delay message delivery to the module if
its queue is to long - using the module's add_msg_cb(), but I think that
that would only cause the bearerbox's MT queue to grow too long and
thrash bearerbox's routing thread - I've seen the same behaviour in
smsbox: when MOs were delivered too fast, smsbox started thrashing. we
solved that problem by running a few more smsboxs on the same machine,
that way the smsbox doesn't thrash, but since MOs are now delivered as
fast as they come, so are MTs, and those cause bearerbox to thrash.
BTW - we do not use HTTPS, but only HTTP calls (to the application). the
module in use is custom made.
--
Oded Arbel
m-Wise Inc.
[EMAIL PROTECTED]
"There is always a holiday somewhere."
-- Avi Savag
> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, March 21, 2002 12:34 PM
> To: Oded Arbel
> Cc: Kannel-devel (E-mail)
> Subject: Re: [BUG] list implementation too slow.
>
>
> Hi Oded & List
>
> Oded Arbel wrote:
> >
> > Hi list.
> >
> > Lately we've been doing some very high capacity testing on
> Kannel , and
> > found out some interesting stuff. mainly as queues (managed
> by lists)
> > are filling up to over a few hundreds of messages, the boxes start
> > thrashing.
> > I think this is directly related to the List implementation
> - it's just
> > too sssslllloooowwww. when we have more then a few hundreds
> of messages
> > in the List, extracting one item can sometimes take
> anywhere from 2 to 4
> > seconds (!!!).
> >
> > Does any one have any information or experience regarding that ?
>
> I send 500000 msg through Kannel and had a similar experience. Kannel
> does
> have a peak performance of 350 msg/s (with test_cimd2 sending true
> service
> request SMs and hello world server answering them; requests were http
> ones
> over our intranet). But long time performance lags, bearerbox grabbing
> most
> of cpu time. And yes, this happens when queues grow long.
>
> (As an aside, Kannel *without* https does 1300 msg/s. And "long term"
> means
> about an hour.)
>
> Aarno
>
