I've decided to give a bit more attention to issues 217 (http:// code.google.com/p/smslib/issues/detail?id=217) and 236 (http:// code.google.com/p/smslib/issues/detail?id=236). Issue 217 affect the previous version, but is about pieces of code which were changed in the latest one - let alone it leads to message loss. Issue 236 is strange enough for itself...
In the latest versions, I've changed the multitasking design of SMSLib from plain threads to a ThreadPoolExecutor implementation. This is supposed to be lighter and possibly more manageable. My stress tests were made with multiple gateways failing one after the other. This would give me a chance to check for both message loss as well as for the correct task scheduling (mainly the QueueManager tasks). As long as Queue check interval was high (> 1.5 seconds - a good value for modems), everything was ok. Then I decided to stress things up a bit. Assuming that you are working with HTTP gateways, a 1.5 second queue processing interval is too high - so I've started lowering it. At one point, the ThreadPoolExecutor begun to act funny: Each task was called multiple times, tasks were failing to be disabled/removed and tasks were called continously and exclusively - all other tasks, like the Watchdog, were "suspended". The only way to get out of this was to press Ctrl-C... My feeling, solely from these tests, is that the ThreadPoolExecutor is not performing well for fast switching tasks. I don't know if anybody knows something more - I would appreciate some feedback. As it stands now, SMSLib is not performing very well under stress tests. So I have two options: either fall back to the pure multithread model (which I, as a traditional guy, like :p) or implement my own (mini) ThreadPoolExecutor which will affect only one source file. Any ideas? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "SMSLib User Group" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/SMSLib?hl=en -~----------~----~----~----~------~----~------~--~---
