You can probably perform some benchmarks for the different strategies and see how they perform for the various parameters that are important for your application (throughput, latency, memory load, CPU load, whatever else you deem important).
As brother BrowserUK has explained, there's virtually nothing you can do from Perl that will affect what your stack will do in getting data from point A to point B.
Depending on how important some of your parameters are, you may find yourself abandoning Perl and going with an implementation written in C. That may take longer to develop, but you will almost certainly get better performance. As always, Your Mileage May Vary.
In reply to Re: Optimizing TCP packet usage with IO::Socket::INET or similar
by talexb
in thread Optimizing TCP packet usage with IO::Socket::INET or similar
by Bloehdian
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |