From: Zeyu Jin <jinzeyu@huawei.com>
To: <quintela@redhat.com>, <dgilbert@redhat.com>
Cc: qemu-devel@nongnu.org, Zeyu Jin <jinzeyu@huawei.com>,
zhang.zhanghailiang@huawei.com
Subject: [PATCH v2 0/6]
Date: Fri, 27 Nov 2020 17:31:22 +0800 [thread overview]
Message-ID: <20201127093122.2451-1-jinzeyu@huawei.com> (raw)
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(-)
--
2.27.0
next reply other threads:[~2020-11-27 9:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-27 9:31 Zeyu Jin [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-05-15 6:26 [PATCH v2 0/6] vanitha.channaiah
2019-05-07 4:30 Sam Bobroff
2013-12-02 11:08 Andre Przywara
2013-12-02 14:52 ` Ian Campbell
2013-12-04 12:16 ` Andre Przywara
2013-12-04 12:29 ` Ian Campbell
2010-07-22 16:29 [PATCH V2 0/6] Marc Kleine-Budde
2009-07-21 22:13 [PATCH v2 0/6] Glauber Costa
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=20201127093122.2451-1-jinzeyu@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 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.