qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Denis Plotnikov <dplotnikov@virtuozzo.com>
To: "dgilbert@redhat.com" <dgilbert@redhat.com>,
	"quintela@redhat.com" <quintela@redhat.com>,
	"eblake@redhat.com" <eblake@redhat.com>,
	"armbru@redhat.com" <armbru@redhat.com>
Cc: Denis Lunev <den@virtuozzo.com>,
	"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PING PING PING] [PATCH 0/3] migration: add sztd compression
Date: Thu, 25 Apr 2019 16:17:13 +0000	[thread overview]
Message-ID: <6955ecd7-7573-99a7-db0a-6f6afe86370f@virtuozzo.com> (raw)
In-Reply-To: <4b9f5045-d4b2-fa10-ab8a-39eaf6ed220c@virtuozzo.com>



On 05.04.2019 14:40, Denis Plotnikov wrote:
> ping!
> 
> On 26.03.2019 18:51, Denis Plotnikov wrote:
>> ping ping ping ping ping!
>>
>> On 18.03.2019 10:53, Denis Plotnikov wrote:
>>> ping ping ping ping!
>>>
>>> On 11.03.2019 11:20, Denis Plotnikov wrote:
>>>> ping ping ping!
>>>>
>>>> On 04.03.2019 18:10, Denis Plotnikov wrote:
>>>>> ping!
>>>>>
>>>>> On 26.02.2019 16:15, Denis Plotnikov wrote:
>>>>>> zstd date compression algorithm shows better performance on data 
>>>>>> compression.
>>>>>> It might be useful to employ the algorithm in VM migration to 
>>>>>> reduce CPU usage.
>>>>>> A user will be able to choose between those algorithms, therefor 
>>>>>> compress-type
>>>>>> migration parameter is added.
>>>>>>
>>>>>> Here are some results of performance comparison zstd vs gzip:
>>>>>>
>>>>>> host: i7-4790 8xCPU @ 3.60GHz, 16G RAM
>>>>>> migration to the same host
>>>>>> VM: 2xVCPU, 8G RAM total
>>>>>> 5G RAM used, memory populated with postgreqsl data
>>>>>> produced by pgbench performance benchmark
>>>>>>
>>>>>>
>>>>>> Threads: 1 compress – 1 decompress
>>>>>>
>>>>>> zstd provides slightly less compression ratio with almost the same
>>>>>> CPU usage but copes with RAM  compression roghly 2 times faster
>>>>>>
>>>>>> compression type              zlib       |      zstd
>>>>>> ---------------------------------------------------------
>>>>>> compression level          1       5     |   1       5
>>>>>> compression ratio          6.92    7.05  |   6.69    6.89
>>>>>> cpu idle, %                82      83    |   86      80
>>>>>> time, sec                  49      71    |   26      31
>>>>>> time diff to zlib, sec                      -25     -41
>>>>>>
>>>>>>
>>>>>> Threads: 8 compress – 2 decompress
>>>>>>
>>>>>> zstd provides the same migration time with less cpu consumption
>>>>>>
>>>>>> compression type         none  |        gzip(zlib)    |          zstd
>>>>>> ------------------------------------------------------------------------------ 
>>>>>>
>>>>>> compression level        -     |  1      5       9    |   1       
>>>>>> 5       15
>>>>>> compression ratio        -     |  6.94   6.99    7.14 |   6.64    
>>>>>> 6.89    6.93
>>>>>> time, sec                154   |  22     23      27   |   23      
>>>>>> 23      25
>>>>>> cpu idle, %              99    |  45     30      12   |   70      
>>>>>> 52      23
>>>>>> cpu idle diff to zlib          |                      |  -25%    
>>>>>> -22%    -11%
>>>>>>
>>>>>>
>>>>>> Denis Plotnikov (3):
>>>>>>        migration: rework compression code for adding more data 
>>>>>> compressors
>>>>>>        hmp: add compress-type parameter to migration parameters
>>>>>>        migration: add zstd compression
>>>>>>
>>>>>>       configure             |  26 ++++
>>>>>>       hmp.c                 |   8 ++
>>>>>>       migration/migration.c |  45 ++++++-
>>>>>>       migration/migration.h |   1 +
>>>>>>       migration/qemu-file.c |  39 ++----
>>>>>>       migration/qemu-file.h |  18 ++-
>>>>>>       migration/ram.c       | 291 
>>>>>> ++++++++++++++++++++++++++++++++++--------
>>>>>>       qapi/migration.json   |  26 +++-
>>>>>>       8 files changed, 369 insertions(+), 85 deletions(-)
>>>>>>
>>>>>
>>>>
>>>
>>
> 

-- 
Best,
Denis

  parent reply	other threads:[~2019-04-25 16:17 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-26 13:15 [Qemu-devel] [PATCH 0/3] migration: add sztd compression Denis Plotnikov
2019-02-26 13:15 ` [Qemu-devel] [PATCH 1/3] migration: rework compression code for adding more data compressors Denis Plotnikov
2019-02-26 13:15 ` [Qemu-devel] [PATCH 2/3] hmp: add compress-type parameter to migration parameters Denis Plotnikov
2019-02-26 13:15 ` [Qemu-devel] [PATCH 3/3] migration: add zstd compression Denis Plotnikov
2019-03-04 15:10 ` [Qemu-devel] [PATCH 0/3] migration: add sztd compression Denis Plotnikov
2019-03-07  8:39   ` Denis Plotnikov
2019-03-11  8:20   ` Denis Plotnikov
     [not found]     ` <5c342066-30b6-e492-e23a-cb5accbfb11a@virtuozzo.com>
     [not found]       ` <53b5c677-870e-56a0-402d-7fdc985ec3f5@virtuozzo.com>
2019-04-05 11:40         ` [Qemu-devel] [PINGl] " Denis Plotnikov
2019-04-05 11:40           ` Denis Plotnikov
2019-04-05 11:40         ` [Qemu-devel] [PING] " Denis Plotnikov
2019-04-05 11:40           ` Denis Plotnikov
2019-04-25 16:17           ` Denis Plotnikov [this message]
2019-04-25 16:17             ` [Qemu-devel] [PING PING PING] " Denis Plotnikov
2019-03-06 11:32 ` [Qemu-devel] " no-reply
2020-01-24 12:43 ` Juan Quintela
2020-01-27  7:19   ` Denis Plotnikov

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=6955ecd7-7573-99a7-db0a-6f6afe86370f@virtuozzo.com \
    --to=dplotnikov@virtuozzo.com \
    --cc=armbru@redhat.com \
    --cc=den@virtuozzo.com \
    --cc=dgilbert@redhat.com \
    --cc=eblake@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=quintela@redhat.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).