Re: [PATCH] Guaranteed throughput smsc-independent

On Wed, Jun 10, 2009 at 09:51:08AM +0300, Nikos Balkanas wrote:
> Hi Donald,
> 
> I think you hit the nail exactly on the head. AFAIK, there is a single thread
> at this point, sms_router, that is implementing bb_smscconn_sent. Therefore
> all sms in the outgoing smscs should be delayed. Kannel doesn't raise threads
> on demand.

Sorry I don't get your point, each smsc is delay on it's own according to my
tests (4 fake smsc with 10sms/s load balanced).

> There may be an additional issue. This approach, which delays everything by a
> set amount if there is a throughput constraint, will utilize exactly half the

Uh?

> available bandwidth. If for example an smsc has a throughput of 10 sms/1',
> and there is a queue of 20 sms, In the old way, assuming it works correctly,
> the first 10 should be send at once at time 0, and the rest at atime 1' with
> an average delay of 30"/sms. With this approach, 1 sms would be sent every
> 6", with an average delay of 1'/sms.

Sorry, I don't get this, could you maybe explain it in another way?

If you got 20 sms in the queue and a throughput of 10, they'll be send in 2
seconds. 10 during the first second and 2 during the second second ;). Even
more, with that algorithm you might take a sample of length N seconds and you
should only find throughput*N outgoing messages (with each message separated by
1/throughput seconds).

> Coupled with the previous point, it could spell problems for queues in large installations that use many smscs to load balance.
> 
> The advantage is that it offers solid throughput handling.
> 
> I am a wap person, so I leave this decision for peoaple with a lot of smss.

I'll be answering the other mails soon.

Thanks for your input.

  Damián Viano(Des).