[c-nsp] what limits bw on a tcp stream?

[Ramcharan, Vijay A]

First guess is probably latency since you mentioned that you can push
more if you do several sessions. Do a bandwidth/delay/product
calculation to figure out what you can reasonably expect for a single
session given the latency and bandwidth between the two sites. 

I used a similar calculation to find out why we were only able to do
about 3Mbps over a DS3 from NY to SF. We're using WAEs at either end to
increase throughput for single session transfers. 
We saw the same issues as you're seeing. i.e. Single file transfer
topping out at 3Mbps. Multiple transfers use more of the available
bandwidth. 
 
Vijay Ramcharan 
 
 


-----Original Message-----
From: cisco-nsp-bounces at puck.nether.net
[mailto:cisco-nsp-bounces at puck.nether.net] On Behalf Of matthew zeier
Sent: Friday, November 16, 2007 9:49 AM
To: cisco-nsp at puck.nether.net
Subject: [c-nsp] what limits bw on a tcp stream?


I have gear in Amsterdam and in San Jose.  Pushing log files from 
Amsterdam to San Jose through rsync seems to top out at 7Mbps even 
though the box doing the push is pushing much more out to the Internet. 
  If I run several rsync's it goes quicker so I know I have the
bandwidth.

What's limiting me?
_______________________________________________
cisco-nsp mailing list  cisco-nsp at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/