> Kalle Marjola wrote:
> >
> > On Thu, 21 Mar 2002, Oded Arbel wrote:
> >
> > > 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.
> >
> > The solution to this is to fix all code so that outgoing messages
> > have higher priority than incoming ones, i.e. do not read anything
> > from bufefrs before outgoing messages have been sent. NOTE: You need
> > to set conn() buffer size, otherwise this does not help as things
> > get added to its internal buffer... I did this for my modified
> > version and got rid of growing size (in memory) and slowdown.
> >
> > (however, I do not know how SMSC would react if the socket gets filled up
> > because the other end is not reading it fast enough..)
I think that we should at least test this approach. There is no reason
to
accept a new request when there are old requests in the queue. Kalle,
can you
send the priority patch ?
Aarno
