["Dennis Schneck" <dennisschneck@xxxxxx>]

 

 

thanks i will try

 

 

 

Gesendet: Montag, 28. August 2017 um 17:30 Uhr
Von: "Hugo van der Kooij" <hugo.van.der.kooij@xxxxxxxxx>
An: "Community support list for Wireshark" <wireshark-users@xxxxxxxxxxxxx>
Betreff: Re: [Wireshark-users] How to find the bottleneck?

 

Dennis,

 

The obvious think to check is the latency. Remote usually means more latency and if the protocol is not design to do this efficient you will get poor results on remote locations with a higher latency.

 

Compare packet captures for both client and look carefully at the timing. I expect that you have taken time to look at the various instruction clips on youtube regarding latency and Wireshark.

 

They will teach you a lot.

 

Met vriendelijke groet / With kind regards,

Hugo

 

 

Hugo van der Kooij
network engineer

 

T: +31 15 888 0 345	F: +31 15 888 0 445
E: hugo.van.der.kooij@xxxxxxxxx	I: www.qsight.nl

Arnhem - Delft - Veldhoven
 

 

Van: Wireshark-users [mailto:wireshark-users-bounces@xxxxxxxxxxxxx] Namens Dennis Schneck
Verzonden: Monday, 28 August, 2017 14:37
Aan: wireshark-users@xxxxxxxxxxxxx
Onderwerp: [Wireshark-users] How to find the bottleneck?

 

Hello,
the following scenario

headquarter:  Server (AIX) and client (Windows)

branch: client (Windows)

 

If the Clients from the branch open a project from the server in the headquarter
it takes about 5 times longer than the same project open in headquarters.
The bandwith from the branch is 1 GB/s for the hole company.
So OK it takes longer in the branch but 5 times.

The Data is on the Storage System.

How to find the bottleneck in the network ?
The networkadmin is sure all is fine.

 

made a IO Graph from "tcp.seq" from one of some sample Data I got from the Users

 

SPW = BAD = branch

SPG = GOOD = headquarter

Thanks
Dennis

 

 

 

 

 

___________________________________________________________________________ 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