From: Peter Xu <peterx@redhat.com>
To: Chuang Xu <xuchuangxclwt@bytedance.com>
Cc: qemu-devel@nongnu.org, dgilbert@redhat.com, quintela@redhat.com,
pbonzini@redhat.com, david@redhat.com, f4bug@amsat.org,
mst@redhat.com, zhouyibo@bytedance.com
Subject: Re: [RFC v3 0/3] migration: reduce time of loading non-iterable vmstate
Date: Fri, 16 Dec 2022 12:11:57 -0500 [thread overview]
Message-ID: <Y5ym3ayBoRNxzT5s@x1n> (raw)
In-Reply-To: <20221213133510.1279488-1-xuchuangxclwt@bytedance.com>
Chuang,
On Tue, Dec 13, 2022 at 09:35:07PM +0800, Chuang Xu wrote:
> Here are the test results:
> test vm info:
> - 32 CPUs 128GB RAM
> - 8 16-queue vhost-net device
> - 16 4-queue vhost-user-blk device.
>
> time of loading non-iterable vmstate
> before about 210 ms
> after about 40 ms
It'll be also great if you can attach more information in the cover letter
in the next post. For example:
- Per your investigation, what's the major influential factor for the
memory updates? Besides the number of devices, does the number of
queues also matter? Is there anything else?
- Total downtime comparison (only if above is only part of the downtime)
- The nic used in the test.
Thanks,
--
Peter Xu
prev parent reply other threads:[~2022-12-16 17:13 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-13 13:35 [RFC v3 0/3] migration: reduce time of loading non-iterable vmstate Chuang Xu
2022-12-13 13:35 ` [RFC v3 1/3] memory: add depth assert in address_space_to_flatview Chuang Xu
2022-12-14 16:03 ` Chuang Xu
2022-12-14 21:38 ` Peter Xu
2022-12-15 16:04 ` Peter Xu
2022-12-20 14:27 ` Chuang Xu
2022-12-15 16:51 ` Peter Maydell
2022-12-20 14:28 ` Chuang Xu
2022-12-20 15:02 ` Peter Xu
2022-12-13 13:35 ` [RFC v3 2/3] virtio: support delay of checks in virtio_load() Chuang Xu
2022-12-13 16:31 ` Peter Xu
2022-12-14 16:02 ` Chuang Xu
2022-12-13 13:35 ` [RFC v3 3/3] migration: reduce time of loading non-iterable vmstate Chuang Xu
2022-12-16 17:11 ` Peter 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=Y5ym3ayBoRNxzT5s@x1n \
--to=peterx@redhat.com \
--cc=david@redhat.com \
--cc=dgilbert@redhat.com \
--cc=f4bug@amsat.org \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
--cc=xuchuangxclwt@bytedance.com \
--cc=zhouyibo@bytedance.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.