Martin Conte Mac Donell schrieb: > On Wed, Feb 4, 2009 at 6:51 PM, Michael Zervakis <[email protected]> wrote: >> I believe that this parameter should be set optimally at msec and not sec to >> handle throttling rates such as 100 messages per sec., because for each >> second we sleep after receiving 0x58 we lose the opportunity to transfer >> these 100 messages, and transmission rate is reduced significantly. > > Maybe the "optimal" solution here is (starting for > SMPP_THROTTLING_MIN_TIME) increase that delay with some sort of > exponential growth until you reach the max defined value.
I agree with Martin here. My "ideal" solution would be an dynamic exponential growth of the sleep time, until we "can" send again, then calibrate to the upper bound (throughput X/sec) by reducing the sleep time again. What we actually want is the "ideal" X/sec. value. We should have 2 ways do get this in the runtime state: a) the user sets it, if he "knows" it. But this may still lead to throttling events. b) the smsc modules itself can handle it dynamically. We can use the user supplied value of a) as a "base" for the upper bound. Now, this is the network flow theory part, now who is going for the implementation part? ;) Stipe -- ------------------------------------------------------------------- Kölner Landstrasse 419 40589 Düsseldorf, NRW, Germany tolj.org system architecture Kannel Software Foundation (KSF) http://www.tolj.org/ http://www.kannel.org/ mailto:st_{at}_tolj.org mailto:stolj_{at}_kannel.org -------------------------------------------------------------------
