qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Zeyu Jin <jinzeyu@huawei.com>
To: <quintela@redhat.com>, <dgilbert@redhat.com>
Cc: qemu-devel@nongnu.org, zhang.zhanghailiang@huawei.com
Subject: Re: [RFC PATCH 0/6] migration: Multi-thread compression with zstd method
Date: Mon, 16 Nov 2020 09:11:20 +0800	[thread overview]
Message-ID: <2aa603e9-f9d4-3c79-eea2-a3ae7f371eea@huawei.com> (raw)
In-Reply-To: <20201109090850.2424-1-jinzeyu@huawei.com>

On 2020/11/9 17:08, Zeyu Jin wrote:
> Currently we have both multi-thread compression and multifd to optimize
> live migration in Qemu. Mulit-thread compression deals with the situation
> where network bandwith is limited but cpu resource adequate. Multifd instead
> aims to take full advantage of network bandwith. Moreover it supports both
> zlib and zstd compression on each channel.
> 
> In this patch series, we did some code refactoring on multi-thread compression
> live migration and bring zstd compression method support for it.
> 
> Below is the test result of multi-thread compression live migration
> with different compress methods. Test result shows that zstd outperforms
> zlib by about 70%.
> 
>  Migration Configuration:
>  Guest 8U 32G
>  compress-threads   8
>  decompress-threads 2
>  compress-level 1
>  bandwidth-limit 100Mbps
> 
>  Test Result:
>  +---------------------+--------------+-------------+
>  |  compress method    |   zlib       |    zstd     |
>  +---------------------+--------------+-------------+
>  |  total time (ms)    |   75256      |    44187    |
>  +---------------------+--------------+-------------+
>  |  downtime(ms)       |   128        |    81       |
>  +---------------------+--------------+-------------+
>  |  transferred ram(kB)|   1576866    |    736117   |
>  +---------------------+--------------+-------------+
>  |  throughput(mbps)   |   172.06     |    137.16   |
>  +---------------------+--------------+-------------+
>  |  total ram(kB)      |   33685952   |    33685952 |
>  +---------------------+--------------+-------------+
> 
> Zeyu Jin (6):
>   migration: Add multi-thread compress method
>   migration: Refactoring multi-thread compress migration
>   migration: Add multi-thread compress ops
>   migration: Add zstd support in multi-thread compression
>   migration: Add compress_level sanity check
>   doc: Update multi-thread compression doc
> 
>  docs/multi-thread-compression.txt |  31 ++-
>  hw/core/qdev-properties-system.c  |  11 +
>  include/hw/qdev-properties.h      |   4 +
>  migration/migration.c             |  56 ++++-
>  migration/migration.h             |   1 +
>  migration/qemu-file.c             |  62 +----
>  migration/qemu-file.h             |   4 +-
>  migration/ram.c                   | 381 +++++++++++++++++++++++++-----
>  monitor/hmp-cmds.c                |  12 +
>  qapi/migration.json               |  26 +-
>  10 files changed, 465 insertions(+), 123 deletions(-)
> 

Ping


      parent reply	other threads:[~2020-11-16  1:12 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-09  9:08 [RFC PATCH 0/6] migration: Multi-thread compression with zstd method Zeyu Jin
2020-11-09  9:08 ` [RFC PATCH 1/6] migration: Add multi-thread compress method Zeyu Jin
2020-11-09 15:57   ` Eric Blake
2020-11-10  2:07     ` Zeyu Jin
2020-11-09  9:08 ` [RFC PATCH 2/6] migration: Refactoring multi-thread compress migration Zeyu Jin
2020-11-09  9:08 ` [RFC PATCH 3/6] migration: Add multi-thread compress ops Zeyu Jin
2020-11-09  9:08 ` [RFC PATCH 4/6] migration: Add zstd support in multi-thread compression Zeyu Jin
2020-11-09  9:08 ` [RFC PATCH 5/6] migration: Add compress_level sanity check Zeyu Jin
2020-11-09  9:08 ` [RFC PATCH 6/6] doc: Update multi-thread compression doc Zeyu Jin
2020-11-16  1:11 ` Zeyu Jin [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=2aa603e9-f9d4-3c79-eea2-a3ae7f371eea@huawei.com \
    --to=jinzeyu@huawei.com \
    --cc=dgilbert@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=quintela@redhat.com \
    --cc=zhang.zhanghailiang@huawei.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).