Generally an application will open as many TCP sessions required in order to perform the required functions. To the best of my knowledge, when a program is created, the programmer can control the number of session allowed to be opened. This means that your application is programmed to work the way you described. Combining the 23 TCP sessions into one would require either your application to be reprogrammed, or some type of smart gateway that will have such capabilities, none of which I know can do this.
In the case you did manage to solve that part of the problem, there is another question. Would the remote end in India be able to handle all 23 combined sessions?
My advice is to contact the creator of your application and present them your concerns and questions, hoping that they will have a solution for you to implement.
From a network administrator's point of view, there are a few step you can take to ensure the application has the necessary bandwidth available so the slowdown effects are maintained to a minimum.
Here are some points:
- Make sure the connection to your ISP is dedicated to the application you are using. Most often, companies will try and use a dedicated line to the Internet for more than what it was originally designed, thus, creating a bottleneck, which in its turn slows everything.
- Check the data going in and out your connection to the Internet. You will often find unwanted traffic entering and exiting your connection to the Internet. This could be the result of someone using peer-to-peer sharing applications (I.E. Kazza) consuming all the valuable bandwidth.
When I first arrive at my company, I found that they were using one 128K ISDN connection for all Internet activities, including remote connections to major IT vendors in the USA (we are located in Greece). The result?
When someone would download their e-mails or browse heavy graphical websites, the remote connection to our customers would simply not respond or at times we would loose the connection!
In this case, the solution was simple, dedicate one 64K ISDN to the vendors and another 64K ISDN to all Internet activity. Of course the Internet was noticeably slower, but everyone was happy, especially the programmers :)
If your setup is somewhat like ours, you could try a similar setup.
Dig Deeper on Network management and monitoring
Related Q&A from Chris Partsenidis
Expert Chris Partsenidis explains what iPerf is and how iPerf commands can help you measure your network's bandwidth, delay, jitter and potential for... Continue Reading
SFP ports enable Gigabit switches to connect to a wide variety of fiber and Ethernet cables in order to extend switching functionality throughout the... Continue Reading
Learn how to understand the difference between bit rate and baud rate in this expert answer. Continue Reading
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.