public inbox for kexec@lists.infradead.org
 help / color / mirror / Atom feed
From: Vivek Goyal <vgoyal@redhat.com>
To: Atsushi Kumagai <kumagai-atsushi@mxc.nes.nec.co.jp>
Cc: kexec@lists.infradead.org, d.hatayama@jp.fujitsu.com,
	dyoung@redhat.com, chaowang@redhat.com
Subject: Re: makedumpfile 1.5.0 takes much more time to dump
Date: Wed, 3 Oct 2012 08:48:13 -0400	[thread overview]
Message-ID: <20121003124813.GB20376@redhat.com> (raw)
In-Reply-To: <20121003163835.c4be2b609deb385aab247beb@mxc.nes.nec.co.jp>

On Wed, Oct 03, 2012 at 04:38:35PM +0900, Atsushi Kumagai wrote:

[..]
> > > If that's going to take time, can we make using of new logic conditional
> > > on a command line option. So that user has the option of using old
> > > logic.
> > > 
> > 
> > Kumagai-san should decide this. 
> 
> I'm not planning to make the cyclic mode optional.
> However, I think the performance issue should be improved even without
> mem_map array logic.
> 
> So, I will try to reduce the number of cycles as few times as possible for v1.5.1,
> the performance issue will be improved.
> To make sure of it, would you re-test with --cyclic-buffer 32768 (32MB), Vivek ?
> Then the result of v1.5.0 is still too bad, I will consider using the old logic 
> as default logic.

Actually chaowang did the testing. In the bug he provided data for 16MB
buffer.

makedumpfile with 16M cyclic buffer,
#1. makedumpfile-1.5.0 -c --message-level 1 -d 31 --cyclic-buffer 16384
real     12m51.886s
user     6m30.710s
sys      6m11.642s
#2. makedumpfile-1.5.0 -E --message-level 1 -d 31 --cyclic-buffer 16384
real     11m24.141s
user     4m25.897s
sys      6m38.116s

Which looks much better than default numbers. Chao, can you please do the
testing with 32MB buffer size and provide the data here.

Thanks
Vivek

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

  reply	other threads:[~2012-10-03 12:48 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-20 20:06 makedumpfile 1.5.0 takes much more time to dump Vivek Goyal
2012-09-21  0:23 ` HATAYAMA Daisuke
2012-09-21  0:43   ` HATAYAMA Daisuke
2012-09-21 13:32   ` Vivek Goyal
2012-09-24  0:51     ` HATAYAMA Daisuke
2012-09-24 14:51       ` Vivek Goyal
2012-10-03  7:38         ` Atsushi Kumagai
2012-10-03 12:48           ` Vivek Goyal [this message]
2012-10-04  1:36             ` HATAYAMA Daisuke
2012-10-04  1:15           ` HATAYAMA Daisuke
     [not found] <1350912018.13097.54.camel@lisamlinux.fc.hp.com>
2012-10-24  7:45 ` Atsushi Kumagai
2012-10-25 11:09   ` Lisa Mitchell
2012-11-06  3:37     ` Atsushi Kumagai

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=20121003124813.GB20376@redhat.com \
    --to=vgoyal@redhat.com \
    --cc=chaowang@redhat.com \
    --cc=d.hatayama@jp.fujitsu.com \
    --cc=dyoung@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox