Wireshark-users: [Wireshark-users] Fw: Re: How to find the bottleneck?
From: "Dennis Schneck" <dennisschneck@xxxxxx>
Date: Tue, 29 Aug 2017 10:45:24 +0200
Hello Anne, Hello Hugo,
I tryed to get some statistics ( smb2, RTT, data usage ).
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?
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
2017-08-28 14:37 GMT+02:00 Dennis Schneck <dennisschneck@xxxxxx>:
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 UsersSPW = BAD = branchSPG = GOOD = headquarter
Thanks
Dennis
___________________________________________________________________________
Sent via: Wireshark-users mailing list <wireshark-users@xxxxxxxxxxxxx>
Archives: https://www.wireshark.org/lists/wireshark-users
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-users
mailto:wireshark-users-request@xxxxxxxxxxxxx?subject=unsubscribe
Attachment:
branch.png
Description: PNG image
Attachment:
branch2.png
Description: PNG image
Attachment:
headquarter.png
Description: PNG image
Attachment:
headquarter2.png
Description: PNG image
Headquarter =========================================================================== SMB2 Service Response Time Statistics - Szenario2_Archiv_erstellen: Index Procedure Calls Min SRT (s) Max SRT (s) Avg SRT (s) Sum SRT (s) --------------------------------------------------------------------------- SMB2 Negotiate Protocol 0 2 0.000321 0.080089 0.040205 0.080410 Session Setup 1 3 0.004582 0.070624 0.041991 0.125973 Session Logoff 2 1 0.000229 0.000229 0.000229 0.000229 Tree Connect 3 2 0.001569 0.065449 0.033509 0.067018 Tree Disconnect 4 2 0.000200 0.000238 0.000219 0.000438 Create 5 246 0.000234 0.016898 0.001055 0.259594 Close 6 284 0.000162 0.003184 0.000454 0.129023 Read 8 2214 0.000262 0.042841 0.008521 18.866242 Write 9 2942 0.000368 0.011055 0.001241 3.650073 Ioctl 11 19 0.003878 0.443808 0.076570 1.454826 Find 14 32 0.000309 0.002893 0.000851 0.027236 Notify 15 3 0.631542 0.656424 0.643896 1.931687 GetInfo 16 421 0.000186 0.096259 0.008743 3.680854 SetInfo 17 3 0.000453 0.001005 0.000662 0.001987 --------------------------------------------------------------------------- Branch =========================================================================== SMB2 Service Response Time Statistics - Szenario_2__packen: Index Procedure Calls Min SRT (s) Max SRT (s) Avg SRT (s) Sum SRT (s) --------------------------------------------------------------------------- SMB2 Negotiate Protocol 0 1 0.007877 0.007877 0.007877 0.007877 Session Setup 1 2 0.008178 0.013942 0.011060 0.022120 Session Logoff 2 1 0.007866 0.007866 0.007866 0.007866 Tree Connect 3 1 0.008156 0.008156 0.008156 0.008156 Tree Disconnect 4 1 0.007882 0.007882 0.007882 0.007882 Create 5 1019 0.000478 0.056522 0.008295 8.452420 Close 6 915 0.000247 0.320530 0.009274 8.485293 Read 8 6911 0.006126 0.051485 0.015365 106.187011 Write 9 841 0.005888 0.032329 0.007638 6.423687 Ioctl 11 563 0.007676 0.009851 0.008125 4.574331 Find 14 144 0.000956 0.037852 0.010477 1.508628 Notify 15 7 0.511076 1.589067 0.798229 5.587600 GetInfo 16 512 0.000478 0.030098 0.008079 4.136519 Break 18 7 0.005709 0.013768 0.008902 0.062311 ---------------------------------------------------------------------------
- Follow-Ups:
- Re: [Wireshark-users] Fw: Re: How to find the bottleneck?
- From: Pedro Tumusok
- Re: [Wireshark-users] Fw: Re: How to find the bottleneck?
- From: Hugo van der Kooij
- Re: [Wireshark-users] Fw: Re: How to find the bottleneck?
- References:
- [Wireshark-users] How to find the bottleneck?
- From: Dennis Schneck
- Re: [Wireshark-users] How to find the bottleneck?
- From: Anne Blankert
- [Wireshark-users] How to find the bottleneck?
- Prev by Date: Re: [Wireshark-users] How to find the bottleneck?
- Next by Date: Re: [Wireshark-users] Fw: Re: How to find the bottleneck?
- Previous by thread: Re: [Wireshark-users] How to find the bottleneck?
- Next by thread: Re: [Wireshark-users] Fw: Re: How to find the bottleneck?
- Index(es):