On Tue, 28 Feb 2012, Adam Tauno Williams wrote:
On Tue, 2012-02-28 at 07:56 -0600, Jack Coats wrote:
In my experience, TCP/IP seems to have about 10% overhead,
I think the overhead depends greatly on the packet size. TCP/IP
overhead can be as high as 98% if your app is streaming packets that
each contain 1 byte of actual data [given a header of 52 bytes] and that
doesn't even include ack/nack traffic or session setup/tear-down. [Hey,
I've seen it happen].
If the application is stupid it can be staggeringly inefficient.
some other points to consider.
1. even a small amount of packet loss can cause significant slowdowns.
2. if you have high latency (satellite or long-distance links) you need to
set your buffer sizes to very large values
3. if a link somewhere along the way gets congested, and has buffers that
are too large, you run into the bufferbloat problem. which can be
summarized as your routers buffering packets so long that they have timed
out by the time they arrive, and so get ignored, both tieing up bandwidth,
and causing your throughput to collapse. If a link is congested, you want
it to drop packets so that the sender will slow down.
but in your case, I agree with others here, it sounds like your
application is sending small packets.
David Lang
_______________________________________________
Tech mailing list
[email protected]
https://lists.lopsa.org/cgi-bin/mailman/listinfo/tech
This list provided by the League of Professional System Administrators
http://lopsa.org/
