All of lore.kernel.org
 help / color / mirror / Atom feed
From: HATAYAMA Daisuke <d.hatayama@jp.fujitsu.com>
To: kumagai-atsushi@mxc.nes.nec.co.jp
Cc: kexec@lists.infradead.org, crash-utility@redhat.com
Subject: Re: [PATCH 0/8] makedumpfile: Add Snappy Compression Support
Date: Thu, 05 Jul 2012 14:36:02 +0900 (JST)	[thread overview]
Message-ID: <20120705.143602.535885847.d.hatayama@jp.fujitsu.com> (raw)
In-Reply-To: <20120705140559.fcaac5a58fa4ab9b6532734c@mxc.nes.nec.co.jp>

From: Atsushi Kumagai <kumagai-atsushi@mxc.nes.nec.co.jp>
Subject: Re: [PATCH 0/8] makedumpfile: Add Snappy Compression Support
Date: Thu, 5 Jul 2012 14:05:59 +0900

> On Tue, 03 Jul 2012 12:07:27 +0900
> HATAYAMA Daisuke <d.hatayama@jp.fujitsu.com> wrote:

> 
> Thank you for your work.
> 
> I will merge your patches into the next version with small addition:
> 
> diff --git a/README b/README
> index ae986d1..638b111 100644
> --- a/README
> +++ b/README
> @@ -45,6 +45,9 @@
>    6.Build with lzo support:
>      # make USELZO=on ; make install
>      The user has to prepare lzo library.
> +  7.Build with snappy support:
> +    # make USESNAPPY=on ; make install
> +    The user has to prepare snappy library.
> 
>  * SUPPORTED KERNELS
>    This makedumpfile supports the following kernels.
> 

Thanks. I overlooked README file...

> 
> In addition, I did brief performance test with your patches:
>   - The source data is a vmcore saved on the disk, it might be sparse data.
>   - makedumpfile writes dumpfile to the same disk as the source data.
>   - execution time is average of 5 times.
> 
>                         |    source     |    zlib     |     LZO     |   snappy  
> ------------------------+---------------+-------------+-------------+-------------
>        size (byte)      | 5,107,498,116 | 242,398,239 | 309,549,499 | 487,542,710 
>   compression  ratio(%) |      ---      |     4.75    |     6.06    |    9.55
>    execution time (sec) |      ---      |      143    |     49.6    |    51.2
> 
> 
> It seems that LZO still has worth in the case that good compression ratio is expected,
> as you said in your benchmark report.
> 

Yes, this is just as I'm assuming. I think it's better to use snappy
for the machine with hundreads of gigabytes or more. For the machine
with less than that, it's still reasonable to use LZO because risk at
the worst case is small.

Also, snappy is well optimized for little endian, 64-bit
machines. Though I don't see this actually to be honest, this might
show considerably bad performance on other archs except for x86_64.

Thanks.
HATAYAMA, Daisuke


_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec

      reply	other threads:[~2012-07-05  5:36 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-03  3:07 [PATCH 0/8] makedumpfile: Add Snappy Compression Support HATAYAMA Daisuke
2012-07-03  3:07 ` [PATCH 1/8] Add dump header for snappy HATAYAMA Daisuke
2012-07-03  3:07 ` [PATCH 2/8] Add command-line processing " HATAYAMA Daisuke
2012-07-03  3:07 ` [PATCH 3/8] Add snappy build support HATAYAMA Daisuke
2012-07-03  3:07 ` [PATCH 4/8] Notify snappy unsupporting when disabled HATAYAMA Daisuke
2012-07-03  3:07 ` [PATCH 5/8] Add compression processing HATAYAMA Daisuke
2012-07-03  3:07 ` [PATCH 6/8] Add uncompression processing HATAYAMA Daisuke
2012-07-03  3:08 ` [PATCH 7/8] Add help message HATAYAMA Daisuke
2012-07-03  3:08 ` [PATCH 8/8] Add manual description HATAYAMA Daisuke
2012-07-05  5:05 ` [PATCH 0/8] makedumpfile: Add Snappy Compression Support Atsushi Kumagai
2012-07-05  5:36   ` HATAYAMA Daisuke [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=20120705.143602.535885847.d.hatayama@jp.fujitsu.com \
    --to=d.hatayama@jp.fujitsu.com \
    --cc=crash-utility@redhat.com \
    --cc=kexec@lists.infradead.org \
    --cc=kumagai-atsushi@mxc.nes.nec.co.jp \
    /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.