Hi Ben, I would start asking the carriers what their throughput is. In all cases I have faced the bottleneck is at the carrier side, even using only one bearerbox and one smsbox.
If you hit their max throughput the operators may ask you to establish additional SMPP connections to their SMSC to "load balance" the traffic. Regards, Rodrigo Cremaschi. On 10/18/06, Ben Suffolk <[EMAIL PROTECTED]> wrote:
Hello, I am currently planning a new service, and the relevant hardware for it. I am after some figures on SMS throughput, both inbound and outbound. My connections will be with SMSCs not modems, and will most likely be smpp3.4, but could in some cases be other SMSC protocols. No messages will be answered locally by kannel, all will be pushed out via http to another server (on the same private LAN, so no network latency issues). All outbound messages will be sent via the http interface, no messages will be replied to via the original outbound http service request. I need to know if anybody has any figures for sustained throughput, and peak throughput for SMS. I'd also be interested if anybody knows the best configuration for maximum throughput, is it better to a a high performance server with several smsboxes and the bearebox, or to have a lower performance server (i.e cheaper) and split the smsboxes from the bearbox, and is it better to have multiple servers each with a single instance of an smsbox (this would obviously be a resilience benefit, but is it a performance one?) At high throughput what resources are used by the bearerbox, and the smsbox. i.e memory intensive?, processor intensive? Regards Ben
