All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vivek Goyal <vgoyal@redhat.com>
To: Cliff Wickman <cpw@sgi.com>
Cc: kumagai-atsushi@mxc.nes.nec.co.jp, d.hatayama@jp.fujitsu.com,
	kexec@lists.infradead.org
Subject: Re: makedumpfile 1.5.4, 734G kdump tests
Date: Thu, 11 Jul 2013 09:06:47 -0400	[thread overview]
Message-ID: <20130711130647.GA20962@redhat.com> (raw)
In-Reply-To: <20130709162403.GA25441@sgi.com>

On Tue, Jul 09, 2013 at 11:24:03AM -0500, Cliff Wickman wrote:

[..]
> UV2000   memory: 734G
> makedumpfile: makedumpfile-1.5.4
> kexec:   git://git.kernel.org/pub/scm/utils/kernel/kexec/kexec-tools.git
> booted with   crashkernel=1G,high crashkernel=192M,low
> non-cyclic mode
> 
> write to       option            init&scan sec.   copy sec.  dump size
> -------------  -----------------           ----   ---------  ---------
> megaraid disk  no compression                19          91      11.7G
> megaraid disk  zlib compression              20         209       1.4G
> megaraid disk  snappy compression            20          46       2.4G
> megaraid disk  snappy compression no mmap    30          72       2.4G
> /dev/null      no compression                19          28          -
> /dev/null      zlib compression              19         206          -
> /dev/null      snappy compression            19          41          -
> 
> Notes and observations
> - Snappy compression is a big win over zlib compression; over 4 times faster
>   with a cost of relatively little disk space.

Thanks for the results Cliff. If it is not too much of trouble, can you
please also test with lzo compression on same configuration. I am 
curious to know how much better snappy performs as compared to lzo.

Thanks
Vivek

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

  parent reply	other threads:[~2013-07-11 13:07 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-09 16:24 makedumpfile 1.5.4, 734G kdump tests Cliff Wickman
     [not found] ` <CAJGZr0JPrBB3cVyVdwJdd6cEUfnXNMuRijb9EOoSy+XmRupv7A@mail.gmail.com>
2013-07-10  9:07   ` HATAYAMA Daisuke
     [not found]     ` <CAJGZr0L7GBqJHaPzgpFxhpF_jmAZfDJYU_=MFxATxnLk13ni4g@mail.gmail.com>
2013-07-10 18:27       ` Cliff Wickman
2013-07-11 13:06 ` Vivek Goyal [this message]
2013-07-12 16:14   ` Cliff Wickman
2013-07-12 16:42     ` Vivek Goyal
2013-07-16  9:22       ` HATAYAMA Daisuke
2013-07-16 14:15         ` Vivek Goyal

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=20130711130647.GA20962@redhat.com \
    --to=vgoyal@redhat.com \
    --cc=cpw@sgi.com \
    --cc=d.hatayama@jp.fujitsu.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.