From: zhenwei pi <pizhenwei@bytedance.com>
To: kwolf@redhat.com, mreitz@redhat.com
Cc: fam@euphon.net, qemu-block@nongnu.org, vsementsov@virtuozzo.com,
qemu-devel@nongnu.org, pizhenwei@bytedance.com
Subject: [Qemu-devel] [PATCH 0/3] Add block size histogram qapi interface
Date: Thu, 20 Jun 2019 16:54:29 +0800 [thread overview]
Message-ID: <1561020872-6214-1-git-send-email-pizhenwei@bytedance.com> (raw)
Set/Clear block size histograms through new command
x-block-size-histogram-set and show new statistics in
query-blockstats results.
This command has been tested for half year on QEMU-2.12, and we found
that 3K+ virtual machines write 25GB/s totally, the block size
histogram like following:
0 ~ 8k: 58% ~ 62%
8k ~ 32k: 10% ~ 12%
32k ~ 128k: 2% ~ 3%
128K ~ 512K: 24% ~ 26%
512K ~ : ...
And the histogram data help us to optimise backend distributed
storage.
zhenwei pi (3):
block/accounting: rename struct BlockLatencyHistogram
block/accounting: introduce block size histogram
qapi: add block size histogram interface
block/accounting.c | 55 ++++++++++++++++++------
block/qapi.c | 26 ++++++++++-
blockdev.c | 56 ++++++++++++++++++++++++
include/block/accounting.h | 12 ++++--
qapi/block-core.json | 105 ++++++++++++++++++++++++++++++++++++++++++++-
5 files changed, 235 insertions(+), 19 deletions(-)
--
2.11.0
next reply other threads:[~2019-06-20 9:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-20 8:54 zhenwei pi [this message]
2019-06-20 8:54 ` [Qemu-devel] [PATCH 1/3] block/accounting: rename struct BlockLatencyHistogram zhenwei pi
2019-06-21 9:45 ` Vladimir Sementsov-Ogievskiy
2019-06-20 8:54 ` [Qemu-devel] [PATCH 2/3] block/accounting: introduce block size histogram zhenwei pi
2019-06-21 9:48 ` Vladimir Sementsov-Ogievskiy
2019-06-20 8:54 ` [Qemu-devel] [PATCH 3/3] qapi: add block size histogram interface zhenwei pi
2019-06-20 14:03 ` Eric Blake
2019-06-21 1:52 ` [Qemu-devel] [External Email] " zhenwei pi
2019-06-21 9:26 ` Vladimir Sementsov-Ogievskiy
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=1561020872-6214-1-git-send-email-pizhenwei@bytedance.com \
--to=pizhenwei@bytedance.com \
--cc=fam@euphon.net \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=vsementsov@virtuozzo.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).