> was one of the significant problems in LBX as large requests could
> > monopolize the wire for a long time. Using one TCP stream per client
> > means each client gets a fair share of the network bandwidth.
>
> Nothing like it. Look up "capture effect". Basically without extra
> correcting factors TCP is "the more you hog the more you win". It is
> very hard to correct the capture effect
Multiple simultaneous TCP connections over the same end to end pair
multiply the capture effect. Congestion is computed on a TCP connection
basis rather than a pairwise basis; in effect, you get more packets in
flight (particularly at application startup or resumption on idle).
Rewriting Keith's statement to say "Using one TCP stream per client means
each client gets at least a little bit of bandwidth in edgewise when there
is a hog", may better.
- Jim
--
Jim Gettys
Cambridge Research Laboratory
HP Labs, Hewlett-Packard Company
[email protected]
lmpx.com only provides a reader for public news (NNTP) servers. It is not
affiliated with the servers or forums shown here and is not responsible for
the content of articles, which is written by their respective authors.