qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: <yang.bin18@zte.com.cn>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] qcow2 performance improve [discuss]
Date: Fri, 27 Jul 2018 18:10:14 +0800 (CST)	[thread overview]
Message-ID: <201807271810146495949@zte.com.cn> (raw)

When use cluster_size=1M qcow2 newly created to test "32k rand write" in the VM,We get low performance within VM。But there are huge “write” requests in HOST which falls into qemu   stack of"perform_cow".


         We found three scene to use cow.

                1.  write cluster have snapshot 

                2.  write img has backing file 

                3.  two concurrent writes happen to the same unallocated cluster.Each write allocates separate cluster and writes data concurrently 。

                For scene 2 and 3,we want to check the necessity before cow.

                For scene 2 ,to check bs->backing,if false ,not cow . 

                For scene 3,if not concurrent writes happen to the same unallocated cluster,not cow.

                 reply	other threads:[~2018-07-27 10:10 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=201807271810146495949@zte.com.cn \
    --to=yang.bin18@zte.com.cn \
    --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).