| SMS Q Processing |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - SMS Issues ⬆ Archive through August 10, 2011 ⬆ |
◄ ► |
| Author | Message | |||
| Rik Clews New member Username: Rikclews Post Number: 19 Registered: 08-2006 |
Hi, I have a quick question, We came across an odd issue regarding delays in processing messages. We have a bind that is restricted to 5 messages / sec (premium rate), along with other unrestricted binds. A customer submitted 10,000 messages routed to the restricted bind, whilst another submitted 100k to use various unrestricted binds. The question is how did NowSMS handle it? Would it be pure first in first out but sending at a rate of 5/sec until the restricted submissions are cleared, or would it send 5 restricted then find the unrestricted to make up full throughput? In this situation everything was handled OK (enough that we didn't see any alerts) but it seems that throughput was significantly reduced for a period during the sends. We just need to figure out how we'll handle the large restricted bind submissions in the future. Many Thanks, Rik | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 7961 Registered: 10-2002 |
Hi Rik, Unless there are speed restrictions defined on individual connections, NowSMS should evenly split messages sent over the connections. However, an asynchronous bind (SMPP window size enabled) may have some slight advantage over a non-async bind. If you are concerned about the restricted bind taking away from the unrestricted bind, you could put a speed limit on the unrestricted bind. The following article explains how to configure this: http://www.nowsms.com/smsc-speed-limits -bn | |||
| Rik Clews New member Username: Rikclews Post Number: 20 Registered: 08-2006 |
We do have a restriction set in the restricted bind of SMSCSendLimit=5, no such restriction on the others. Also, all our messages are specifically routed, which is what made me wonder if NowSMS picks the first message but can't send it due to the restriction, will it go and get the next or will it wait until the restriction has passed - so in this case throttling to 5 messages /sec rather than the expected 100 /sec? | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 7964 Registered: 10-2002 |
Hi Rik, If the route is only using 5 out of 100, it should have a negligible impact. Each connection has its own separate logic thread, so it should not block like you describe. One tip ... since all (or most) of your messages are explicitly routed, add UseRouteQueues=Yes to the [SMSGW] section of SMSGW.INI. This improves the logic of message scanning in a situation where most messages are explicitly routed. -bn | |||
| Rik Clews New member Username: Rikclews Post Number: 21 Registered: 08-2006 |
Thats marvellous, thanks Bryce! | |||
