ceph-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Layton <jlayton@redhat.com>
To: Venky Shankar <vshankar@redhat.com>,
	pdonnell@redhat.com, xiubli@redhat.com
Cc: ceph-devel@vger.kernel.org
Subject: Re: [PATCH v1 0/4] ceph: forward average read/write/metadata latency
Date: Mon, 13 Sep 2021 11:13:00 -0400	[thread overview]
Message-ID: <22e110d00df3d02157222754f01fc6143cb40764.camel@redhat.com> (raw)
In-Reply-To: <20210913131311.1347903-1-vshankar@redhat.com>

On Mon, 2021-09-13 at 18:43 +0530, Venky Shankar wrote:
> 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
> 
> The math involved in keeping track of the average latency and stdev
> seems incorrect, so, this series fixes that up too (closely mimics
> how its done in userspace with some restrictions obviously) as per::
> 
>           NEW_AVG = OLD_AVG + ((latency - OLD_AVG) / total_ops)
>           NEW_STDEV = SQRT(((OLD_STDEV + (latency - OLD_AVG)*(latency - NEW_AVG)) / (total_ops - 1)))
> 
> Note that the cumulative latencies are still forwarded to the MDS but
> the tool (cephfs-top) ignores it altogether.
> 
> Venky Shankar (4):
>   ceph: use "struct ceph_timespec" for r/w/m latencies
>   ceph: track average/stdev r/w/m latency
>   ceph: include average/stddev r/w/m latency in mds metrics
>   ceph: use tracked average r/w/m latencies to display metrics in
>     debugfs
> 
>  fs/ceph/debugfs.c | 12 +++----
>  fs/ceph/metric.c  | 81 +++++++++++++++++++++++++----------------------
>  fs/ceph/metric.h  | 64 +++++++++++++++++++++++--------------
>  3 files changed, 90 insertions(+), 67 deletions(-)
> 

This looks reasonably sane. I'll plan to go ahead and pull this into the
testing kernels and do some testing with them. If anyone has objections
(Xiubo?) let me know and I can take them out.

Thanks,
-- 
Jeff Layton <jlayton@redhat.com>


  parent reply	other threads:[~2021-09-13 15:13 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-13 13:13 [PATCH v1 0/4] ceph: forward average read/write/metadata latency Venky Shankar
2021-09-13 13:13 ` [PATCH v1 1/4] ceph: use "struct ceph_timespec" for r/w/m latencies Venky Shankar
2021-09-13 13:13 ` [PATCH v1 2/4] ceph: track average/stdev r/w/m latency Venky Shankar
2021-09-13 13:13 ` [PATCH v1 3/4] ceph: include average/stddev r/w/m latency in mds metrics Venky Shankar
2021-09-13 13:13 ` [PATCH v1 4/4] ceph: use tracked average r/w/m latencies to display metrics in debugfs Venky Shankar
2021-09-13 15:13 ` Jeff Layton [this message]
2021-09-13 15:21   ` [PATCH v1 0/4] ceph: forward average read/write/metadata latency Jeff Layton
2021-09-13 15:41     ` Venky Shankar
2021-09-14 12:53   ` 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=22e110d00df3d02157222754f01fc6143cb40764.camel@redhat.com \
    --to=jlayton@redhat.com \
    --cc=ceph-devel@vger.kernel.org \
    --cc=pdonnell@redhat.com \
    --cc=vshankar@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).