From: Jingbai Ma <jingbai.ma@hp.com>
To: Vivek Goyal <vgoyal@redhat.com>,
HATAYAMA Daisuke <d.hatayama@jp.fujitsu.com>,
zhangyanfei@cn.fujitsu.com, "Mitchell,
Lisa (MCLinux in Fort Collins)" <lisa.mitchell@hp.com>,
"kumagai-atsushi@mxc.nes.nec.co.jp"
<kumagai-atsushi@mxc.nes.nec.co.jp>,
"Eric W. Biederman" <ebiederm@xmission.com>,
cpw@sgi.com, akpm@linux-foundation.org,
"yinghai@kernel.org" <yinghai@kernel.org>
Cc: "kexec@lists.infradead.org" <kexec@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
jingbai.ma@hp.com
Subject: makedumpfile parallel dumping test
Date: Mon, 22 Apr 2013 19:12:33 +0800 [thread overview]
Message-ID: <51751B21.4080505@hp.com> (raw)
Hi all,
I have done some experiments on parallel kernel dumping. I would like to
share the test result with you. Hope it helps.
Test environment:
Machine: HP ProLiant DL980 G7 with 4TB RAM.
CPU: Intel(R) Xeon(R) CPU E7- 2860 @ 2.27GHz (8 sockets, 10 cores) (4
CPU were enabled the 2nd kernel by nr_cpus=4)
Kernel 3.9.0-rc7
kexec-tools 2.0.4
makedumpfile v1.5.3 with lzo library
crashkernel=4096M (I have tested with 2048M but failed with OOM on 3 or
4 parallels dumping in cyclic mode)
I didn't get a real multipath storage device, so I just put dump files
on 4 different disks via 3 HP Smart Array controllers. (mounted on /0,
/1, /2 and /3 in the capture kernel)
Measured time like this (for example: lzo compression, non-cyclic, 4
parallels):
time makedumpfile -l -non-cyclic --split --message-level 23 -d 31
/proc/vmcore /0/vmcore_0 /1/vmcore_1 /2/vmcore_2 /3/vmcore_3
I run several tests with different option, parallels from 1 to 4, and
combined with zlib and lzo compression.
Test result:
-----------------------------------------------------------------
| |Parallels 1|Parallels 2|Parallels 3|Parallels 4|
-----------------------------------------------------------------
|zlib cyclic | 42m25.321s| 34m0.168s| 29m44.908s| 28m50.387s|
-----------------------------------------------------------------
|zlib non-cyclic| 42m7.842s| 28m28.275s| 23m25.750s| 21m6.476s|
-----------------------------------------------------------------
|lzo cyclic | 23m40.010s| 18m19.932s| 21m47.903s| 22m47.605s|
-----------------------------------------------------------------
|lzo non-cyclic | 20m45.749s| 16m42.045s| 15m41.070s| 15m18.605s|
-----------------------------------------------------------------
--
Thanks,
Jingbai Ma
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
reply other threads:[~2013-04-22 11:12 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=51751B21.4080505@hp.com \
--to=jingbai.ma@hp.com \
--cc=akpm@linux-foundation.org \
--cc=cpw@sgi.com \
--cc=d.hatayama@jp.fujitsu.com \
--cc=ebiederm@xmission.com \
--cc=kexec@lists.infradead.org \
--cc=kumagai-atsushi@mxc.nes.nec.co.jp \
--cc=linux-kernel@vger.kernel.org \
--cc=lisa.mitchell@hp.com \
--cc=vgoyal@redhat.com \
--cc=yinghai@kernel.org \
--cc=zhangyanfei@cn.fujitsu.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