BTW check the User's guide p 28 group smsc: throughput # (messages/sec)
BR, Nikos ----- Original Message ----- From: Nikos Balkanas To: [email protected] Sent: Monday, November 17, 2008 6:10 PM Subject: Re: Kannel memory Leak and throttling issue Best case would be someone really familiar with the code, to recognise the issue just from your description (that's not me). Otherwise, IMHO one important issue is to reproduce it at lab conditions. I have written a C multithreaded wap client which I have used to benchmark/stress test kannel cvs. I am working on a similar for PPG. I have observed nothing like that in wapbox or bearerbox. Currently I am not interested in SMS, so I have no plans to develop any load generators. Typical settings used are 1000x1000, i.e. 1000 threads X 1000 requests each. If you were to feed such an input to a disconnected smsbox, it should show immediately. In the lab one can use a lot of tools to detect memory leaks. Regards, Nikos ----- Original Message ----- From: Alison Reidy To: [email protected] Sent: Monday, November 17, 2008 5:05 PM Subject: Kannel memory Leak and throttling issue I’m trying to find out if we can throttle the messages per second rate that Kannel submit’s to the provider. Also, related to this is that our SMSC disconnects us when we’ve exceeded our throttle, and Kannel stores these messages that it can’t send. At this point it seems, , kannel’s Virtual memory just increases until the OS causes the system to crash. So the problem is two fold: when kannel can’t send messages (because the SMSC’s throttle has been exceeded), it’s holding them and trying again, and that retry seems to have a memory leak which causes the system to crash. Any ideas? Thanks Alison Reidy
