qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Chuang Xu <xuchuangxclwt@bytedance.com>
To: pbonzini@redhat.com
Cc: qemu-devel@nongnu.org, dgilbert@redhat.com, quintela@redhat.com,
	peterx@redhat.com, david@redhat.com, philmd@linaro.org
Subject: Re: [PATCH v8 0/6] migration: reduce time of loading non-iterable vmstate
Date: Fri, 16 Jun 2023 16:15:02 +0800	[thread overview]
Message-ID: <93b9e037-9c26-e37e-3327-bc7f91e18ad2@bytedance.com> (raw)
In-Reply-To: <20230317081904.24389-1-xuchuangxclwt@bytedance.com>

Hi, Paolo,

A few months ago, Juan told me that this series requires your or someone 
familiar with memory API's feedback.

Could you please review it and provide some suggestions?

On 2023/3/17 下午4:18, Chuang Xu wrote:
> In this version:
>
> - delete useless line change.
> - update comments and commit messages.
>
> The duration of loading non-iterable vmstate accounts for a significant
> portion of downtime (starting with the timestamp of source qemu stop and
> ending with the timestamp of target qemu start). Most of the time is spent
> committing memory region changes repeatedly.
>
> This patch packs all the changes to memory region during the period of	
> loading non-iterable vmstate in a single memory transaction. With the
> increase of devices, this patch will greatly improve the performance.
>
> Here are the test1 results:
> test info:
> - Host
>    - Intel(R) Xeon(R) Platinum 8362 CPU
>    - Mellanox Technologies MT28841
> - VM
>    - 32 CPUs 128GB RAM VM
>    - 8 16-queue vhost-net device
>    - 16 4-queue vhost-user-blk device.
>
> 	time of loading non-iterable vmstate     downtime
> before		 112 ms			  	  285 ms
> after		 20 ms			  	  194 ms
>
>
> In test2, we keep the number of the device the same as test1, reduce the
> number of queues per device:
>
> Here are the test2 results:
> test info:
> - Host
>    - Intel(R) Xeon(R) Platinum 8362 CPU
>    - Mellanox Technologies MT28841
> - VM
>    - 32 CPUs 128GB RAM VM
>    - 8 1-queue vhost-net device
>    - 16 1-queue vhost-user-blk device.
>
> 	time of loading non-iterable vmstate     downtime
> before		 65 ms			 	  151 ms
>
> after		 19 ms			  	  100 ms
>
>
> In test3, we keep the number of queues per device the same as test1, reduce
> the number of devices:
>
> Here are the test3 results:
> test info:
> - Host
>    - Intel(R) Xeon(R) Platinum 8362 CPU
>    - Mellanox Technologies MT28841
> - VM
>    - 32 CPUs 128GB RAM VM
>    - 1 16-queue vhost-net device
>    - 1 4-queue vhost-user-blk device.
>
> 	time of loading non-iterable vmstate     downtime
> before		 24 ms			  	  51 ms
> after		 9 ms			 	  36 ms
>
>
> As we can see from the test results above, both the number of queues and
> the number of devices have a great impact on the time of loading non-iterable
> vmstate. The growth of the number of devices and queues will lead to more
> mr commits, and the time consumption caused by the flatview reconstruction
> will also increase.
>
> Please review, Chuang
>
Thanks!


      parent reply	other threads:[~2023-06-16  8:16 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-17  8:18 [PATCH v8 0/6] migration: reduce time of loading non-iterable vmstate Chuang Xu
2023-03-17  8:18 ` [PATCH v8 1/6] memory: Reference as->current_map directly in memory commit Chuang Xu
2023-03-17  8:19 ` [PATCH v8 2/6] rcu: Introduce rcu_read_is_locked() Chuang Xu
2023-03-17  8:19 ` [PATCH v8 3/6] memory: Introduce memory_region_transaction_do_commit() Chuang Xu
2023-03-17  8:19 ` [PATCH v8 4/6] memory: Add do_commit() and sanity check in address_space_to_flatview Chuang Xu
2023-03-17  8:19 ` [PATCH v8 5/6] migration: Reduce time of loading non-iterable vmstate Chuang Xu
2023-03-17  8:19 ` [PATCH v8 6/6] memory: Introduce address_space_to_flatview_rcu() Chuang Xu
2023-06-16  8:15 ` Chuang Xu [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=93b9e037-9c26-e37e-3327-bc7f91e18ad2@bytedance.com \
    --to=xuchuangxclwt@bytedance.com \
    --cc=david@redhat.com \
    --cc=dgilbert@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=peterx@redhat.com \
    --cc=philmd@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=quintela@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).