Skip to content
This repository has been archived by the owner on Nov 1, 2022. It is now read-only.

High Traffic Performance Increase #23

Open
ashbrener opened this issue Mar 3, 2016 · 0 comments
Open

High Traffic Performance Increase #23

ashbrener opened this issue Mar 3, 2016 · 0 comments

Comments

@ashbrener
Copy link

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.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant