| BroadBand Upload Capacity & SMS Sending |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - MMS & Advanced Issues ⬆ Archive through April 05, 2007 ⬆ |
◄ ► |
| Author | Message | |||
| Rhea New member Username: Rhea Post Number: 5 Registered: 08-2006 |
What is the optimum BroadBand Upload Capacity for Sending SMS? I know ofcourse its dependant on the Throughput, but if so how can it be calculated so that i can know the Broadband Speed required to have an efficient running system. | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 6418 Registered: 10-2002 |
Hi Rhea, Since this question is directly related to another thread that you have posted, I'm going to cross reference it here ... mainly for helping others that may have similar questions. http://support.nowsms.com/discus/messages/485/17148.html Upload capacity or broadband speed can be a factor ... but it is important to keep in mind that SMS messages themselves are very small, they contain very little data. The SMPP protocol is a lot more "chatty" than other protocols. Submit a 160 character message to the server, receive back a 20 byte response. Let's say you're sending 30 messages per second over the upload link ... 30 * 160 = 4800 ... let's round it up to 5KB/sec ... or effectively 50Kb/sec, as data transfer speeds are generally measured in bits instead of bytes. That's not a lot of bandwidth, even if my rough calculations are missing some overhead. However, it's a lot of small packets. And I don't know how much of a difference that makes. In any event ... typical broadband throughput doesn't seem to be as much of an issue in these types of situations as latency. If you can't use SMPP windowing, then you have to wait for a response from the other server before the next message can be submitted. The latency in the connection between client and server become a big issue here, as in addition to the processing delay at the server, you've got the travel time for the request to make it to the server and for the response to make it back. Windowing gets around this because you can have multiple requests outstanding between client and server ... and the client doesn't have to wait for the response before it sends the next request. For your specific problems, I think figuring out why the provider returns "Message Queue Full" errors when you use larger windows would be the most helpful in resolving your speed problems. I don't think broadband speed is an issue, as long as you've got something reasonable (like at least 1Mb/sec). -bn | |||
