From: Peter Xu <peterx@redhat.com>
To: "Liu, Yuan1" <yuan1.liu@intel.com>
Cc: "Wang, Yichen" <yichen.wang@bytedance.com>,
"Fabiano Rosas" <farosas@suse.de>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Daniel P. Berrangé" <berrange@redhat.com>,
"Eduardo Habkost" <eduardo@habkost.net>,
"Marc-André Lureau" <marcandre.lureau@redhat.com>,
"Thomas Huth" <thuth@redhat.com>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>,
"Eric Blake" <eblake@redhat.com>,
"Markus Armbruster" <armbru@redhat.com>,
"Laurent Vivier" <lvivier@redhat.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
"Hao Xiang" <hao.xiang@linux.dev>,
"Zou, Nanhai" <nanhai.zou@intel.com>,
"Ho-Ren (Jack) Chuang" <horenchuang@bytedance.com>
Subject: Re: [PATCH v6 1/5] docs/migration: add qatzip compression feature
Date: Tue, 16 Jul 2024 10:50:13 -0400 [thread overview]
Message-ID: <ZpaIpXyVWdLHGkbB@x1n> (raw)
In-Reply-To: <PH7PR11MB59410143A089733E8FAC5A36A3A22@PH7PR11MB5941.namprd11.prod.outlook.com>
On Tue, Jul 16, 2024 at 02:34:07AM +0000, Liu, Yuan1 wrote:
> > -----Original Message-----
> > From: Yichen Wang <yichen.wang@bytedance.com>
> > Sent: Tuesday, July 16, 2024 6:13 AM
> > To: Peter Xu <peterx@redhat.com>; Fabiano Rosas <farosas@suse.de>; Paolo
> > Bonzini <pbonzini@redhat.com>; Daniel P. Berrangé <berrange@redhat.com>;
> > Eduardo Habkost <eduardo@habkost.net>; Marc-André Lureau
> > <marcandre.lureau@redhat.com>; Thomas Huth <thuth@redhat.com>; Philippe
> > Mathieu-Daudé <philmd@linaro.org>; Eric Blake <eblake@redhat.com>; Markus
> > Armbruster <armbru@redhat.com>; Laurent Vivier <lvivier@redhat.com>; qemu-
> > devel@nongnu.org
> > Cc: Hao Xiang <hao.xiang@linux.dev>; Liu, Yuan1 <yuan1.liu@intel.com>;
> > Zou, Nanhai <nanhai.zou@intel.com>; Ho-Ren (Jack) Chuang
> > <horenchuang@bytedance.com>; Wang, Yichen <yichen.wang@bytedance.com>
> > Subject: [PATCH v6 1/5] docs/migration: add qatzip compression feature
> >
> > From: Yuan Liu <yuan1.liu@intel.com>
> >
> > add Intel QATzip compression method introduction
> >
> > Signed-off-by: Yuan Liu <yuan1.liu@intel.com>
> > Reviewed-by: Nanhai Zou <nanhai.zou@intel.com>
> > Reviewed-by: Peter Xu <peterx@redhat.com>
> > Reviewed-by: Yichen Wang <yichen.wang@bytedance.com>
> > ---
> > docs/devel/migration/features.rst | 1 +
> > docs/devel/migration/qatzip-compression.rst | 251 ++++++++++++++++++++
> > 2 files changed, 252 insertions(+)
> > create mode 100644 docs/devel/migration/qatzip-compression.rst
> >
> > diff --git a/docs/devel/migration/features.rst
> > b/docs/devel/migration/features.rst
> > index 58f8fd9e16..8f431d52f9 100644
> > --- a/docs/devel/migration/features.rst
> > +++ b/docs/devel/migration/features.rst
> > @@ -14,3 +14,4 @@ Migration has plenty of features to support different
> > use cases.
> > CPR
> > qpl-compression
> > uadk-compression
> > + qatzip-compression
> > diff --git a/docs/devel/migration/qatzip-compression.rst
> > b/docs/devel/migration/qatzip-compression.rst
> > new file mode 100644
> > index 0000000000..72fa3e2826
> > --- /dev/null
> > +++ b/docs/devel/migration/qatzip-compression.rst
> > @@ -0,0 +1,251 @@
> > +==================
> > +QATzip Compression
> > +==================
> > +In scenarios with limited network bandwidth, the ``QATzip`` solution can
> > help
> > +users save a lot of host CPU resources by accelerating compression and
> > +decompression through the Intel QuickAssist Technology(``QAT``) hardware.
>
> Hi Yichen
>
> Thanks for adding the part of Performance Testing with QATzip, I wonder if we
> can remove Performance Testing with QATzip part and directly add the following
> content.
>
> Here, we use a typical example of limited bandwidth to illustrate the advantages
> of QATzip. If the user is interested in qatzip, he still needs to verify the performance
> by himself.
>
> +The following test was conducted using 8 multifd channels and 10Gbps network
> +bandwidth. The results show that, compared to zstd, ``QATzip`` significantly
> +saves CPU resources on the sender and reduces migration time. Compared to the
> +uncompressed solution, ``QATzip`` greatly improves the dirty page processing
> +capability, indicated by the Pages per Second metric, and also reduces the
> +total migration time.
> +
> +::
> +
> + VM Configuration: 16 vCPU and 64G memory
> + VM Workload: all vCPUs are idle and 54G memory is filled with Silesia data.
> + QAT Devices: 4
> + |-----------|--------|---------|----------|----------|------|------|
> + |8 Channels |Total |down |throughput|pages per | send | recv |
> + | |time(ms)|time(ms) |(mbps) |second | cpu %| cpu% |
> + |-----------|--------|---------|----------|----------|------|------|
> + |qatzip | 16630| 28| 10467| 2940235| 160| 360|
> + |-----------|--------|---------|----------|----------|------|------|
> + |zstd | 20165| 24| 8579| 2391465| 810| 340|
> + |-----------|--------|---------|----------|----------|------|------|
> + |none | 46063| 40| 10848| 330240| 45| 85|
> + |-----------|--------|---------|----------|----------|------|------|
Yes this looks much simpler and better. The 10GBps test isn't that useful
at least, especially with nocomp numbers absent. I didn't say when looking
previously, but it'll be better to clarify the numbers.
Yuan, thanks so much for reviewing all the relevant patches. It's very
helpful to us.
--
Peter Xu
next prev parent reply other threads:[~2024-07-16 14:50 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-15 22:12 [PATCH v6 0/5] Implement QATzip compression method Yichen Wang
2024-07-15 22:12 ` [PATCH v6 1/5] docs/migration: add qatzip compression feature Yichen Wang
2024-07-16 2:34 ` Liu, Yuan1
2024-07-16 14:50 ` Peter Xu [this message]
2024-07-15 22:12 ` [PATCH v6 2/5] meson: Introduce 'qatzip' feature to the build system Yichen Wang
2024-07-16 3:03 ` Liu, Yuan1
2024-07-15 22:12 ` [PATCH v6 3/5] migration: Add migration parameters for QATzip Yichen Wang
2024-07-19 6:05 ` Markus Armbruster
2024-07-15 22:12 ` [PATCH v6 4/5] migration: Introduce 'qatzip' compression method Yichen Wang
2024-07-16 14:30 ` Liu, Yuan1
2024-07-19 6:05 ` Markus Armbruster
2024-07-15 22:12 ` [PATCH v6 5/5] tests/migration: Add integration test for " Yichen Wang
2024-07-16 14:32 ` Liu, Yuan1
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=ZpaIpXyVWdLHGkbB@x1n \
--to=peterx@redhat.com \
--cc=armbru@redhat.com \
--cc=berrange@redhat.com \
--cc=eblake@redhat.com \
--cc=eduardo@habkost.net \
--cc=farosas@suse.de \
--cc=hao.xiang@linux.dev \
--cc=horenchuang@bytedance.com \
--cc=lvivier@redhat.com \
--cc=marcandre.lureau@redhat.com \
--cc=nanhai.zou@intel.com \
--cc=pbonzini@redhat.com \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=thuth@redhat.com \
--cc=yichen.wang@bytedance.com \
--cc=yuan1.liu@intel.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).