| NowSMS sizing |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - SMS Issues ⬆ Archive through July 28, 2010 ⬆ |
◄ ► |
| Author | Message | |||
| Giuseppe Plagenza New member Username: Gplagenza Post Number: 1 Registered: 06-2010 |
We are planning to use NowSMS to add SMS capabilities to an IT solution. There is any documentation or benchmark that can help in properly sizing the NowSMS component, based on considerations like: amount of received or sent SMS per second ? Thanks in advance. Giuseppe. | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 2265 Registered: 08-2008 |
Hi Giuseppe, Are you asking about hardware requirements? The different usage scenarios for NowSMS make it very difficult to give hardware recommendations. How many messages per second are you targeting? Generally speaking, unless you're looking at more than 10 messages per second, you can make due with just about any desktop computer offered by the major manufacturers. Higher speed connections can benefit from faster processors. More processor cores and/or hyperthreading (HT) support is also a plus as you get to larger configurations. Routing messages to a large number of outbound SMSC connections can put additional strain on a system, where multiple cores can really add benefit. NowSMS is not particularly memory intensive, but if you are going to have large bulk blasts of messages that need to be temporarily queued, faster hard drives and more memory for disk caching can be helpful. I would recommend using an SMPP provider, preferably one that supports async SMPP. It can be a challenge to get beyond 3 to 5 messages per second over a single SMPP connection unless you use async SMPP. It is a limitation of the protocol, and exact performance without async SMPP will vary considerably. You can use multiple SMSC connections (SMPP or otherwise) to get additional message throughput. Another consideration ... if you are processing inbound SMS messages via HTTP callback scripts, performance can be limited by how quickly your scripts process the messages. It is easy to allocate more threads in NowSMS for more concurrent received message callbacks. But I mention this because part of your sizing issues may be for an HTTP server that is going to process callback scripts for received messages. So ... a lot of things can vary based upon your planned usage scenario. If you want to give me more details about your planned usage scenario, I can get more specific. Or if you'd like more clarification on any of the things that I mentioned (or failed to mention), please ask. -- Des NowSMS Support | |||
