Slow transfer of delivery reports | Search |
NowSMS Support Forums ⬆ NowSMS Support - SMS Issues ⬆ Archive through December 14, 2010 ⬆ |
◄ ► |
Author | Message | |||
Alexandre Frequent Contributor Username: Alexd Post Number: 131 Registered: 01-2008 |
Hi! To NowSMS is connected client for send messages. After sending messages, delivery reports are accumulated in client login \ Q and go with a speed of 12-20 messages per second. On his side reception rate is set to 100 messages per second. Thank you in advance for your reply. Because of what may occur such a loss in speed? His smpp client is connected to nowsms in mode: 1 Sender and 1 reciver. I'm not the first time facing the fact that some customers complain about slow transfer of delivery reports. This is a problem in the slow transfer of delivery reports from novsms to another customer? Or there may be another reason? The client uses the program Kannel | |||
Des - NowSMS Support Board Administrator Username: Desosms Post Number: 2556 Registered: 08-2008 |
Hi Alexandre, Is it only delivery reports? (Or maybe the user does not receive large volumes of other messages so it is only noticeable with delivery reports.) NowSMS does not use Async SMPP for sending over client connections, so this could be a factor. I am going to investigate this further. I know that many clients could break if Async SMPP were to be used, so we would not want to implement by default. But I know from experience that sending without Async support will top out around 10mps depending on latency between client and server. -- Des NowSMS Support | |||
Alexandre Frequent Contributor Username: Alexd Post Number: 132 Registered: 01-2008 |
Yeah only delivery reports. I check with Wireshark and it show 10-13 packet per second. Thank in advance | |||
Des - NowSMS Support Board Administrator Username: Desosms Post Number: 2579 Registered: 08-2008 |
Hi Alexandre, I haven't forgotten about this one. We've been working to add async mode SMPP support for delivering messages from NowSMS to client connections. Currently NowSMS only supports async mode SMPP for connections where NowSMS is the SMPP client ... not when NowSMS is the SMPP server. That is because that has been our primary focus for performance has been, as for most people, this is the critical path. Without async mode support, if the client and server are not on the same LAN ... or if the client has any delay in sending the deliver acknowledgment ... the throughput will be limited. NowSMS server to NowSMS client, I can do about 150 messages per second if they are on the same LAN. Performance does drop the greater the network latency is between the client and server. Async mode SMPP is the best way to overcome this performance drag ... which is what we already do when NowSMS is the SMPP client. We're still testing an update that adds async SMPP support into the NowSMS SMPP Server. I'm not good at estimates, but it will still likely be a week or two before this is ready to be posted. -- Des NowSMS Support | |||
Alexandre Frequent Contributor Username: Alexd Post Number: 136 Registered: 01-2008 |
Ok. Big thanks. I`ll wait for this update | |||
Des - NowSMS Support Board Administrator Username: Desosms Post Number: 2623 Registered: 08-2008 |
An update that adds async mode support for connections where NowSMS is the server side has been posted to http://www.nowsms.com/download/nowsms20101104.zip. This setting is not enabled by default. Here is a description:
| |||
Alexandre Frequent Contributor Username: Alexd Post Number: 137 Registered: 01-2008 |
ooo! very good update! SMPPServerAsyncWindowSize=## what max value can be? If i add [SMPPServerAsyncWindowSize] then settings can be like: [SMPPServerAsyncWindowSize] somelogin=## ? And don`t need add SMPPServerAsyncWindowSize=## to the [SMSGW] section? | |||
Des - NowSMS Support Board Administrator Username: Desosms Post Number: 2630 Registered: 08-2008 |
It's hard to say what the right value is to use. That typically requires experimentation. I usually go for setting it to my desired mps speed. But our implementation is slightly different on the server side vs. the client side, so I don't have enough experience giving a recommended value or recommended maximum.
That is correct. It means that a window size of ## will be enabled for delivering messages to the "somelogin" client account. Other clients will use the default value, which is 0 ... meaning that async mode is disabled for delivering messages to them. For most installations, the [SMPPServerAsyncWindowSize] section will be appropriate. This allows you to selectively enable async mode only for clients that are known to be able to handle it. -- Des NowSMS Support |