Hi
On medium sized hardware (Intel Xeon, 8GB RAM, IDE RAID) we have tested
our Kannel with fakesmsc with huge speeds.
In real world while being connected to 9 mobile operators (some of them
multiple binds) we have reached 150-170 SMS per second.
It is actually 150 incoming SMS per sec. We same time sent the response
SMS to clients and rerouted all messages to SMPPbox and served the
third-party client.
During that test we monitored network traffic (it was very low, 1MBit
network connection should handle it), server processor mostly worked on
apache/php thread, not the bearerbox/smsbox/smppbox threads. Main
limiting factor limiting the speeds are mobile operators.
Illimar
Millions of requests per second? Someone added some extra zeroes just
for fun I guess, or perhaps that figure was per _day_ instead?
Honestly, all those requests-per-second figures are completely
meaningless out of context. There are too many factors involved in the
outcome to make a realistic guess about an sms gateway's throughput.
Usually the carrier's capabilities or your application's speed are the
bottleneck. Network latency as well, but there are a lot of other
factors into the equation (bandwidth, hardware, number of binds, other
applications running on the same box, filesystem, hdd speed, etc, etc).
In short: the only way to tell is to really test your setup for real.
On my own experience, we achieved figures of hundreds of messages per
second, and kannel was never the limiting factor: it's usually the
applications not processing fast enough, or the smsc binds being
limited by the carrier.
Regards,
Alejandro
On Wed, Nov 18, 2009 at 11:59 AM, denis bahati <[email protected]
<mailto:[email protected]>> wrote:
Which hardware and network resources can cause kannel to process
few requests per second. Someone told me kannel can handle
millions of request per second.
