>* Are you sure the branch has a 1 GB/s connection to HQ? 1GB/s possible, but quite good for current standards.
This branch yes
>If traffic is routed over public internet between branch and HQ, there are likely some bottlenecks beyond your control
not is managed from the provider
>* Is there network latency between branch and headquarters? Even on high bandwidth connections, network latency can cause low data >transfer rates because some protocols are very chatty: the next packet is sent only after receiving acknowledgment for the previous packet. >With high latency networks, this may result in sometimes very poor transfer speeds
it is in the same country so I hope it is not to much... sorry did not have details about
How to Measuring, make sense between 2 clients 1 in headquarter and one in branch ?
tool ?
Gesendet: Montag, 28. August 2017 um 17:35 Uhr
Von: "Anne Blankert" <anne.blankert@xxxxxxxxx>
An: "Community support list for Wireshark" <wireshark-users@xxxxxxxxxxxxx>
Betreff: Re: [Wireshark-users] How to find the bottleneck?
* Are you sure the branch has a 1 GB/s connection to HQ? 1GB/s possible, but quite good for current standards.
* The network is as slow as the slowest link. Are you sure that the slowest link between the branch client and HQ server is 1GB/sec? If traffic is routed over public internet between branch and HQ, there are likely some bottlenecks beyond your control
* Is there network latency between branch and headquarters? Even on high bandwidth connections, network latency can cause low data transfer rates because some protocols are very chatty: the next packet is sent only after receiving acknowledgment for the previous packet. With high latency networks, this may result in sometimes very poor transfer speeds
___________________________________________________________________________ Sent via: Wireshark-users mailing list Archives: https://www.wireshark.org/lists/wireshark-users Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-users mailto:wireshark-users-request@xxxxxxxxxxxxx?subject=unsubscribe