From: Stefan Hajnoczi <stefanha@gmail.com>
To: PANKAJ RAWAT <pankajr141@gmail.com>
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] effect of cluster_size on qcow2 performance during expansion
Date: Thu, 23 Feb 2012 09:17:03 +0000 [thread overview]
Message-ID: <CAJSP0QWWTGkDM3QxuKCkmFMAKGrQ+joaZd4K+i6ba6uqxjsDdw@mail.gmail.com> (raw)
In-Reply-To: <CABZruFAisb9a-xuY7ORWFv0LvV0FpDA8fjzmtHvft-X4KYVBbA@mail.gmail.com>
On Thu, Feb 23, 2012 at 8:24 AM, PANKAJ RAWAT <pankajr141@gmail.com> wrote:
> Here are the reading taken through fio tool during write operation
>
>
> Cluster size : 32K 587Mb/sec (aggrb MB/sec)
>
>
> Cluster size : 64K 697Mb/sec (aggrb MB/sec)
>
> Cluster size : 1M 440Mb/sec (aggrb MB/sec)
>
>
> Cluster size : 2M 289Mb/sec (aggrb MB/sec)
>
> as in above it can bee seen that the 64k is performing better
>
> can any one tell why ?
Yes. Please see the other email thread you created on this topic.
Stefan
prev parent reply other threads:[~2012-02-23 9:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-23 8:24 [Qemu-devel] effect of cluster_size on qcow2 performance during expansion PANKAJ RAWAT
2012-02-23 9:17 ` Stefan Hajnoczi [this message]
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=CAJSP0QWWTGkDM3QxuKCkmFMAKGrQ+joaZd4K+i6ba6uqxjsDdw@mail.gmail.com \
--to=stefanha@gmail.com \
--cc=pankajr141@gmail.com \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).