From: "Aurélien Aptel" <aaptel@suse.com>
To: Pavel Shilovsky <piastryyy@gmail.com>, Steve French <smfrench@gmail.com>
Cc: CIFS <linux-cifs@vger.kernel.org>
Subject: Re: [PATCH] Add a dynamic tracepoint for smb3_cmd_enter
Date: Thu, 28 Feb 2019 12:56:09 +0100 [thread overview]
Message-ID: <87o96wnn3a.fsf@suse.com> (raw)
In-Reply-To: <CAKywueRw7aBj3AhSADbU1pSWuTNa=7LKaXWNPrhB6isf2x-DWw@mail.gmail.com>
Pavel Shilovsky <piastryyy@gmail.com> writes:
> Thanks, now we have a great tool to start analyzing client latency.
> The more advanced step would be to start aggregate latency numbers and
> count percentiles (especially for specific commands).
As a side note, Wireshark can report some of this.
tshark -z smb2,srt -r dump.pcap
SMB2 SRT Statistics:
Filter: smb2.cmd
Index Commands Calls Min SRT Max SRT Avg SRT Sum SRT
5 Create 14759 0.000387 0.035268 0.001288 19.003702
6 Close 14713 0.000253 0.029454 0.000629 9.260241
14 Find 27468 0.000237 0.035798 0.000678 18.634827
16 GetInfo 983 0.000276 0.020349 0.000553 0.543487
SRT is Service Response time. You have RTT and other metrics as well. I
discovered this via Ronnie's SDC talk from years back [1] very good
reference. You can also graph all sorts of things, look at the slides 28
and on.
1: https://wiki.wireshark.org/Presentations?action=AttachFile&do=view&target=RonnieSahlberg_UsingWireshark.pdf
--
Aurélien Aptel / SUSE Labs Samba Team
GPG: 1839 CB5F 9F5B FB9B AA97 8C99 03C8 A49B 521B D5D3
SUSE Linux GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg)
prev parent reply other threads:[~2019-02-28 11:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-27 3:28 [PATCH] Add a dynamic tracepoint for smb3_cmd_enter Steve French
2019-02-27 19:30 ` Pavel Shilovsky
2019-02-28 11:56 ` Aurélien Aptel [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87o96wnn3a.fsf@suse.com \
--to=aaptel@suse.com \
--cc=linux-cifs@vger.kernel.org \
--cc=piastryyy@gmail.com \
--cc=smfrench@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.