From: Pavel Butsykin <pbutsykin@virtuozzo.com>
To: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>,
qemu-block@nongnu.org, qemu-devel@nongnu.org
Cc: kwolf@redhat.com, mreitz@redhat.com, stefanha@redhat.com,
den@openvz.org, famz@redhat.com, jsnow@redhat.com
Subject: Re: [Qemu-devel] [PATCH v2] iotest 055: refactor and speed up
Date: Tue, 16 Aug 2016 14:44:21 +0300 [thread overview]
Message-ID: <57B2FC95.7040809@virtuozzo.com> (raw)
In-Reply-To: <1470748523-13856-1-git-send-email-vsementsov@virtuozzo.com>
On 09.08.2016 16:15, Vladimir Sementsov-Ogievskiy wrote:
> Source disk is created and filled with test data before each test case.
> Instead initialize it once for the whole unit.
>
> Test disk filling patterns are merged into one pattern.
>
> Also TestSetSpeed used different image_len for source and target (by
> mistake) - this is automatically fixed here.
>
> Signed-off-by: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
> ---
>
> v2: rebase on block-next, as compression test pattern differs, merge patterns.
>
> Need review from Pavel, is new merged disk filling pattern ok for you?
>
> Also, removed from commit message performance measurements. On block-next this test
> is too long for other reasons, so for qcow speed is not such significant: for qcow2
> I have 7min:33s -> 6min:45s.
>
>
> tests/qemu-iotests/055 | 52 +++++++++++++++++---------------------------------
> 1 file changed, 18 insertions(+), 34 deletions(-)
>
Reviewed-by: Pavel Butsykin <pbutsykin@virtuozzo.com>
But unfortunately, here the main slowing factor is vmdk compression.
next prev parent reply other threads:[~2016-08-16 14:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-09 13:15 [Qemu-devel] [PATCH v2] iotest 055: refactor and speed up Vladimir Sementsov-Ogievskiy
2016-08-16 11:44 ` Pavel Butsykin [this message]
2016-08-29 12:53 ` Max Reitz
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=57B2FC95.7040809@virtuozzo.com \
--to=pbutsykin@virtuozzo.com \
--cc=den@openvz.org \
--cc=famz@redhat.com \
--cc=jsnow@redhat.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
--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 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.