| Performance |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - SMS Issues ⬆ Archive through September 15, 2003 ⬆ |
◄ ► |
| Author | Message | |||
| Solomon |
How many messages per second do you software send out? | |||
| Solomon |
What is your upgrade policy and ToS? | |||
| Bryce Norwood - NowSMS Support (Bryce) |
One year support and upgrades are included in purchase. After one year, to continue a support and upgrade agreement is a 20% of the purchase price per annum. On the messages per second, let me see if I can find a good testing tool to help us test that. On the GSM modem side of things, its relatively easy to test because things are so slow (only 6 to 8 per minute per modem). But on the SMPP side, obviously you're talking about hundreds or thousands of times faster. Let me see what tools I can locate to perform a test. -bn | |||
| Bryce Norwood - NowSMS Support (Bryce) |
Solomon, I found some software to help me run some preliminary tests. To test the HTTP interface for submitting messages, I used some older Microsoft software named "INetLoad". It's not available on the Microsoft site any more, but there are still copies floating around out on the internet. To test the SMPP interface, I connected the gateway to a homegrown test program. Basically, we're considering adding the capability to act as an SMPP server (in addition to the current SMPP client capability) in a future release, so we have an SMPP server test program that accepts messages but doesn't do any processing against them. I was able to consistently get in excess of 60 messages per second (excess of 3600 messages per minute) through this test configuration. The gateway PC was a Pentium 4, 1.9Ghz, 256MB RAM, running Windows XP. However, I was a little suspicious about these results, because the CPU load was not maxing out on the gateway PC, and it appeared that the gateway would be able to process a far greater number of messages. So I tried some more tests. I tried a test where INetLoad submitted messages via HTTP but there was no SMSC attached to the gateway. Again, it maxed out at 60 messages per second, but the CPU load was not maxing out. I then connected the SMPP SMSC test program, and let the gateway fire off the queued messages. The queued messages were transmitted via SMPP in excess of 200 messages per second. What to make of all of this? Well, it appears that INetLoad is a bottleneck. To reliably test configurations in excess of 60 messages per second, I think we need some better HTTP testing software. On this particular PC configuration, based on these observations, I would expect it to be able to process in excess of 120 messages per second. For all I know, with the right testing software, the HTTP interface may be able to keep up with the SMPP interface at over 200 messages per second on this configuration. If you have any suggestions for how you would like to see things tested, I'd be open for more suggestions. It does appear that there are some simple things that we could do to tweak performance quite significantly. -bn | |||
| Elsie M Rhoades |
I have two brothers in Cave Junction, OR with a phone system from Frontier. They cannot use my 877 follow me number from their area. Why? Can this be fixed? I am going to be RV'ing full time and want them to be able to reach me with my follow me number. Elsie Rhoades 8137979 Acct #1700334486 | |||
| Bryce Norwood - NowSMS Support (Bryce) |
Elsie, I have no idea what you are talking about. You're obviously not at the correct web site. -bn | |||
