Recommendations:
1) Use iperf in TCP mode to test the performance
2) use iperf in UDP mode to test the performance
This is the best way to quickly triage the issue and determine if
it's actual bandwidth issue or something else.
It's quite common for variou
Sounds like a combination of packet loss and small TCP receive windows. If
you can, grab a packet capture and make sure to get the TCP setup. That
should show you what's happening under the hood.
Also, I should mention that I totally hosed the units in my first reply.
:) That's what I get for hu
I apologize I should have said it starts out about 3 meg max and slows to about
400kpbs for most of the transfer.
> On Oct 31, 2014, at 3:27 PM, John Neiberger wrote:
>
> With a max bandwidth of 25 Mbps and a 40ms RTT, the max is more like 14MB/s
> or 1.75 Mbps.
>
> https://www.switch.ch/n
With a max bandwidth of 25 Mbps and a 40ms RTT, the max is more like 14MB/s
or 1.75 Mbps.
https://www.switch.ch/network/tools/tcp_throughput/index.html?mss=1460&rtt=80&loss=1e-06&bw=25&rtt2=35&win=64&Calculate=Calculate
But that's only if either endpoint is stuck at a 64 KB receive window. A
quic
On 31 October 2014 18:32, Zachary Frederick wrote:
> We have been having a problem receiving software releases from our
> developer. The releases are typically around 1G in size. The developer’s
> connection is a 100m metro fiber with TW Telecom, our connection is a 25m
> Comcast Enterprise Fibe
We have been having a problem receiving software releases from our developer.
The releases are typically around 1G in size. The developer’s connection is a
100m metro fiber with TW Telecom, our connection is a 25m Comcast Enterprise
Fiber.
Our traffic graphs show very little utilization of our
6 matches
Mail list logo
