search

Roave / shorty

An asynchronous SMPP client and server built on Node.js. Shorty is sponsored and maintained by SMS Cloud, a subsidiary of Roave
http://roave.com/
GNU General Public License v3.0
92 stars 52 forks source link

High Traffic Performance Increase #23

Open ashbrener opened 8 years ago

ashbrener commented 8 years ago

If we want to connect to multiple SMPP servers, using a single clustered node.js app would it be advisable to create multiple Shorty client instances in each worker?

What are the performance implications here, and would it even be a good idea to open multiple sockets per worker to each single SMPP server? (Suggested pull request #22)

Would also be interested in completing TRANSMITTER and RECEIVER functionality that do not appear currently available in Shorty. Seems to be the right model according to this article:

SMPP Connection Types – Sender, Receiver, Transceiver The type of connection that you use will depend on the preferences and policies of your SMPP service provider. Separate “sender” and “receiver” connections generally offer the best performance under extreme loads, however your provider may wish for you to use a “transceiver” connection to reduce the connection overhead on their server.