public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Johannes Weiner <hannes@cmpxchg.org>
To: Dennis Zhou <dennisszhou@gmail.com>
Cc: Tejun Heo <tj@kernel.org>, Jens Axboe <axboe@kernel.dk>,
	Josef Bacik <jbacik@fb.com>,
	kernel-team@fb.com, linux-block@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] block: make iolatency avg_lat exponentially decay
Date: Wed, 1 Aug 2018 12:02:27 -0400	[thread overview]
Message-ID: <20180801160227.GA8891@cmpxchg.org> (raw)
In-Reply-To: <20180801002559.36261-1-dennisszhou@gmail.com>

On Tue, Jul 31, 2018 at 05:25:59PM -0700, Dennis Zhou wrote:
> From: "Dennis Zhou (Facebook)" <dennisszhou@gmail.com>
> 
> Currently, avg_lat is calculated by accumulating the mean of every
> window in a long running cumulative average. As time goes on, the metric
> becomes less and less useful due to the accumulated history.
> 
> This patch reuses the same calculation done in load averages to make the
> avg_lat metric more lively. Unlike load averages, the avg only advances
> when a window elapses (due to an io). Idle periods extend the most
> recent window. Bucketing is used to limit the history of avg_lat by
> binding it to the window size. So, the window range for 1/exp (decay
> rate) is [1 min, 2.5 min) when windows elapse immediately.
> 
> The current sample window size is exposed in the debug info to enable
> calculation of the window range.
> 
> Signed-off-by: Dennis Zhou <dennisszhou@gmail.com>

Looks great, thanks Dennis. Once the div build error is fixed, please
feel free to add:

Acked-by: Johannes Weiner <hannes@cmpxchg.org>

  parent reply	other threads:[~2018-08-01 15:59 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-01  0:25 [PATCH v2] block: make iolatency avg_lat exponentially decay Dennis Zhou
2018-08-01  4:46 ` kbuild test robot
2018-08-01 15:49 ` Tejun Heo
2018-08-01 16:10   ` Tejun Heo
2018-08-02  6:11     ` Dennis Zhou
2018-08-01 16:02 ` Johannes Weiner [this message]
2018-08-01 16:26 ` Josef Bacik

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=20180801160227.GA8891@cmpxchg.org \
    --to=hannes@cmpxchg.org \
    --cc=axboe@kernel.dk \
    --cc=dennisszhou@gmail.com \
    --cc=jbacik@fb.com \
    --cc=kernel-team@fb.com \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tj@kernel.org \
    /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