Al Boldi wrote:
Toby DiPasquale wrote:
On 9/19/05, Al Boldi <a1426z@xxxxxxxxx> wrote:
Pure TCP. How do you unlimit the TCP connection?
You can only shape/limit connections. You can't make them go faster
(unless they are slower than they should be, and then you have a
tuning/equipment problem, so fix that).
I am running the vanillaKernel in default config.
ifconfig shows no drops,errors,overruns.
Are you implying the default Kernel is misconfigured?
The only thing that throttles TCP throughput is packet loss, window
size and latency.
Plus host and router CPU/line card/interface utilization, device
buffer sizes, link utilization, switch capacity, interrupt load, NIC
quality, retransmissions, amount of RAM, etc, etc. You can get really
involved if you want to.
The system is idle.
One connection gets ~70% throughput.
Two connections get ~90% total throughput.
Window size maybe.
Is this tunable per connection?
Yes, but not to the level you might want. See W. Richard Stevens' UNIX
Network Programming for the particular socket options that can be
played with (TCP_MAXSEG and TCP_WINDOW_CLAMP, in this case; man 7 tcp
will also be enlightening).
Good info!
To some degree you ARE tuning the window size with multiple streams, the
number of unacknowledged bytes will be the sum of all streams. This
problem gets worse with long latency times, getting throughput up
locally is usually possible, while getting good transfer rates over high
latency links is much harder.
--
bill davidsen <davidsen@xxxxxxx>
CTO TMR Associates, Inc
Doing interesting things with small computers since 1979
-
: send the line "unsubscribe linux-net" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
