From: Jeff Layton <jlayton@kernel.org>
To: xiubli@redhat.com, idryomov@gmail.com
Cc: sage@redhat.com, zyan@redhat.com, pdonnell@redhat.com,
ceph-devel@vger.kernel.org
Subject: Re: [PATCH v9 0/5] ceph: add perf metrics support
Date: Mon, 09 Mar 2020 08:09:21 -0400 [thread overview]
Message-ID: <5f1c8c66f573ce499a1232c2346f5baaff413a57.camel@kernel.org> (raw)
In-Reply-To: <1583739430-4928-1-git-send-email-xiubli@redhat.com>
On Mon, 2020-03-09 at 03:37 -0400, xiubli@redhat.com wrote:
> From: Xiubo Li <xiubli@redhat.com>
>
> Changed in V9:
> - add an r_ended field to the mds request struct and use that to calculate the metric
> - fix some commit comments
>
> We can get the metrics from the debugfs:
>
> $ cat /sys/kernel/debug/ceph/0c93a60d-5645-4c46-8568-4c8f63db4c7f.client4267/metrics
> item total sum_lat(us) avg_lat(us)
> -----------------------------------------------------
> read 13 417000 32076
> write 42 131205000 3123928
> metadata 104 493000 4740
>
> item total miss hit
> -------------------------------------------------
> d_lease 204 0 918
> caps 204 213 368218
>
Thanks Xiubo! This looks good. One minor issue with the cap patch, but I
can just fix that up before merging if you're ok with my proposed
change.
Beyond this...while average latency is a good metric, it's often not
enough to help diagnose problems. I wonder if we ought to be at least
tracking min/max latency for all calls too. I wonder if there's way to
track standard deviation too? That would be really nice to have.
Cheers,
--
Jeff Layton <jlayton@kernel.org>
next prev parent reply other threads:[~2020-03-09 12:09 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-09 7:37 [PATCH v9 0/5] ceph: add perf metrics support xiubli
2020-03-09 7:37 ` [PATCH v9 1/5] ceph: add global dentry lease metric support xiubli
2020-03-09 7:37 ` [PATCH v9 2/5] ceph: add caps perf metric for each session xiubli
2020-03-09 11:51 ` Jeff Layton
2020-03-09 12:05 ` Jeff Layton
2020-03-09 12:36 ` Xiubo Li
2020-03-09 18:22 ` Jeff Layton
2020-03-10 0:25 ` Xiubo Li
2020-03-09 12:26 ` Xiubo Li
2020-03-09 7:37 ` [PATCH v9 3/5] ceph: add global read latency metric support xiubli
2020-03-09 7:37 ` [PATCH v9 4/5] ceph: add global write " xiubli
2020-03-09 7:37 ` [PATCH v9 5/5] ceph: add global metadata perf " xiubli
2020-03-09 12:09 ` Jeff Layton [this message]
2020-03-09 12:35 ` [PATCH v9 0/5] ceph: add perf metrics support Xiubo Li
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=5f1c8c66f573ce499a1232c2346f5baaff413a57.camel@kernel.org \
--to=jlayton@kernel.org \
--cc=ceph-devel@vger.kernel.org \
--cc=idryomov@gmail.com \
--cc=pdonnell@redhat.com \
--cc=sage@redhat.com \
--cc=xiubli@redhat.com \
--cc=zyan@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox