From: Venky Shankar <vshankar@redhat.com>
To: jlayton@redhat.com, xiubli@redhat.com
Cc: ceph-devel@vger.kernel.org, Venky Shankar <vshankar@redhat.com>
Subject: [PATCH 0/3] ceph: forward average read/write/metadata latency
Date: Tue, 15 Feb 2022 14:46:54 +0530 [thread overview]
Message-ID: <20220215091657.104079-1-vshankar@redhat.com> (raw)
Right now, cumulative read/write/metadata latencies are tracked
and are periodically forwarded to the MDS. These meterics are not
particularly useful. A much more useful metric is the average latency
and standard deviation (stdev) which is what this series of patches
aims to do.
The userspace (libcephfs+tool) changes are here::
https://github.com/ceph/ceph/pull/41397
Note that the cumulative latencies are still forwarded to the MDS but
the tool (cephfs-top) ignores it altogether.
Latency standard deviation is calculated in `cephfs-top` tool.
Venky Shankar (3):
ceph: track average r/w/m latency
ceph: include average/stdev r/w/m latency in mds metrics
ceph: use tracked average r/w/m latencies to display metrics in
debugfs
fs/ceph/debugfs.c | 2 +-
fs/ceph/metric.c | 44 +++++++++++++++++++++++----------------
fs/ceph/metric.h | 52 +++++++++++++++++++++++++++++++++--------------
3 files changed, 65 insertions(+), 33 deletions(-)
--
2.27.0
next reply other threads:[~2022-02-15 9:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-15 9:16 Venky Shankar [this message]
2022-02-15 9:16 ` [PATCH 1/3] ceph: track average r/w/m latency Venky Shankar
2022-02-15 9:16 ` [PATCH 2/3] ceph: include average/stdev r/w/m latency in mds metrics Venky Shankar
2022-02-15 9:16 ` [PATCH 3/3] ceph: use tracked average r/w/m latencies to display metrics in debugfs Venky Shankar
2022-02-15 11:36 ` Jeff Layton
2022-02-15 11:12 ` [PATCH 0/3] ceph: forward average read/write/metadata latency Xiubo Li
2022-02-15 11:38 ` Jeff Layton
2022-02-15 12:26 ` Venky Shankar
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=20220215091657.104079-1-vshankar@redhat.com \
--to=vshankar@redhat.com \
--cc=ceph-devel@vger.kernel.org \
--cc=jlayton@redhat.com \
--cc=xiubli@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 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.