From: Peter Xu <peterx@redhat.com>
To: guangrong.xiao@gmail.com
Cc: pbonzini@redhat.com, mst@redhat.com, mtosatti@redhat.com,
qemu-devel@nongnu.org, kvm@vger.kernel.org, dgilbert@redhat.com,
wei.w.wang@intel.com, eblake@redhat.com, quintela@redhat.com,
cota@braap.org, Xiao Guangrong <xiaoguangrong@tencent.com>
Subject: Re: [Qemu-devel] [PATCH 0/2] optimize waiting for free thread to do compression
Date: Fri, 21 Dec 2018 16:10:55 +0800 [thread overview]
Message-ID: <20181221081055.GD2996@xz-x1> (raw)
In-Reply-To: <20181213075727.23540-1-xiaoguangrong@tencent.com>
On Thu, Dec 13, 2018 at 03:57:25PM +0800, guangrong.xiao@gmail.com wrote:
> From: Xiao Guangrong <xiaoguangrong@tencent.com>
>
> Currently we have two behaviors if all threads are busy to do compression,
> the main thread mush wait one of them becoming free if @compress-wait-thread
> set to on or the main thread can directly return without wait and post
> the page out as normal one
>
> Both of them have its profits and short-comes, however, if the bandwidth is
> not limited extremely so that compression can not use out all of it bandwidth,
> at the same time, the migration process is easily throttled if we posted too
> may pages as normal pages. None of them can work properly under this case
>
> In order to use the bandwidth more effectively, we introduce the third
> behavior, compress-wait-thread-adaptive, which make the main thread wait
> if there is no bandwidth left or let the page go out as normal page if there
> has enough bandwidth to make sure the migration process will not be
> throttled
>
> Another patch introduces a new statistic, pages-per-second, as bandwidth
> or mbps is not enough to measure the performance of posting pages out as
> we have compression, xbzrle, which can significantly reduce the amount of
> the data size, instead, pages-per-second if the one we want
>
> Performance data
> ================
> We have limited the bandwidth to 300
>
> Used Bandwidth Pages-per-Second
> compress-wait-thread = on 951.66 mbps 131784
>
> compress-wait-thread = off 2491.74 mbps 93495
> compress-wait-thread-adaptive 1982.94 mbps 162529
> = on
Sounds reasonable to me, though it looks like there're only three
options: on, off, adaptive. Should we squash the two parameters?
Thanks,
--
Peter Xu
next prev parent reply other threads:[~2018-12-21 8:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-13 7:57 [Qemu-devel] [PATCH 0/2] optimize waiting for free thread to do compression guangrong.xiao
2018-12-13 7:57 ` [Qemu-devel] [PATCH 1/2] migration: introduce compress-wait-thread-adaptive guangrong.xiao
2018-12-13 7:57 ` [Qemu-devel] [PATCH 2/2] migration: introduce pages-per-second guangrong.xiao
2018-12-21 8:10 ` Peter Xu [this message]
2018-12-24 13:36 ` [Qemu-devel] [PATCH 0/2] optimize waiting for free thread to do compression(Internet mail) xiaoguangrong(Xiao Guangrong)
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=20181221081055.GD2996@xz-x1 \
--to=peterx@redhat.com \
--cc=cota@braap.org \
--cc=dgilbert@redhat.com \
--cc=eblake@redhat.com \
--cc=guangrong.xiao@gmail.com \
--cc=kvm@vger.kernel.org \
--cc=mst@redhat.com \
--cc=mtosatti@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
--cc=wei.w.wang@intel.com \
--cc=xiaoguangrong@tencent.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).