qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Fam Zheng <famz@redhat.com>
To: Max Reitz <mreitz@redhat.com>
Cc: Kevin Wolf <kwolf@redhat.com>,
	qemu-devel@nongnu.org, Stefan Hajnoczi <stefanha@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v5 5/5] qemu-iotests: Add 093 for IO throttling
Date: Wed, 28 Jan 2015 09:59:06 +0800	[thread overview]
Message-ID: <20150128015906.GD8368@ad.nay.redhat.com> (raw)
In-Reply-To: <54C7B970.5080002@redhat.com>

On Tue, 01/27 11:14, Max Reitz wrote:
> On 2015-01-26 at 22:03, Fam Zheng wrote:
> >On Mon, 01/26 15:45, Max Reitz wrote:
> >>On 2015-01-16 at 03:46, Fam Zheng wrote:
> >>>This case utilizes qemu-io command "aio_{read,write} -q" to verify the
> >>>effectiveness of IO throttling options.
> >>>
> >>>It's implemented by driving the vm timer from qtest protocol, so the
> >>>throttling timers are signaled with determinied time duration. Then we
> >>>verify the completed IO requests are within 10% error of bps and iops
> >>>limits.
> >>>
> >>>"null" protocol is used as the disk backend so that no actual disk IO is
> >>>performed on host, this will make the blockstats much more
> >>>deterministic. Both "null-aio" and "null-co" are covered, which is also
> >>>a simple cross validation test for the driver code.
> >>>
> >>>Signed-off-by: Fam Zheng <famz@redhat.com>
> >>>---
> >>>  tests/qemu-iotests/093     | 103 +++++++++++++++++++++++++++++++++++++++++++++
> >>>  tests/qemu-iotests/093.out |   5 +++
> >>>  tests/qemu-iotests/group   |   1 +
> >>>  3 files changed, 109 insertions(+)
> >>>  create mode 100755 tests/qemu-iotests/093
> >>>  create mode 100644 tests/qemu-iotests/093.out
> >>NACK. This literally kills my laptop (I can recover when running this test
> >>in tmpfs (for some reason inexplicable to me, since this uses the null block
> >>drivers...), but I cannot when running it on my HDD).
> >>
> >>Would it be possible to use larger requests and smaller iops? (Or just the
> >>same request size but smaller bps as well)
> >Is it because of CPU or memory? 1000 requests for both read and write seem to
> >be overkilling since we are measuring 1000 bps and 10 iops, please try if
> >reducing to 100 requests works for you.
> 
> Probably memory, since I seem to recall you having the same model as me, but
> I can imagine you having more RAM...
> 
> 100 requests do not work with 128,000 bps/64 iops/10 seconds (because that'd
> be more than 1 MB of data, whereas 100 requests of 4 kB are of course only
> 400 kB), but the following constellations work:

Oops, I changed bps and iops limits in v5 but was talking about 1000/10 here.
We can still lower the limits though. I'll send a v6 for you to try soon.

Fam

  reply	other threads:[~2015-01-28  1:59 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-16  8:46 [Qemu-devel] [PATCH v5 0/5] block: Add a qemu-iotests case for IO throttling Fam Zheng
2015-01-16  8:46 ` [Qemu-devel] [PATCH v5 1/5] qemu-io: Account IO by aio_read and aio_write Fam Zheng
2015-01-26 20:19   ` Max Reitz
2015-01-16  8:46 ` [Qemu-devel] [PATCH v5 2/5] qtest: Add scripts/qtest.py Fam Zheng
2015-01-26 20:22   ` Max Reitz
2015-01-16  8:46 ` [Qemu-devel] [PATCH v5 3/5] qemu-iotests: Add VM method qtest() to iotests.py Fam Zheng
2015-01-26 20:26   ` Max Reitz
2015-01-16  8:46 ` [Qemu-devel] [PATCH v5 4/5] qemu-iotests: Allow caller to disable underscore convertion for qmp Fam Zheng
2015-01-26 20:27   ` Max Reitz
2015-01-16  8:46 ` [Qemu-devel] [PATCH v5 5/5] qemu-iotests: Add 093 for IO throttling Fam Zheng
2015-01-26 20:45   ` Max Reitz
2015-01-27  3:03     ` Fam Zheng
2015-01-27 16:14       ` Max Reitz
2015-01-28  1:59         ` Fam Zheng [this message]
2015-01-28 11:11           ` Markus Armbruster

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=20150128015906.GD8368@ad.nay.redhat.com \
    --to=famz@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=mreitz@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@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).