From: Ingo Molnar <mingo@kernel.org>
To: "Du, Changbin" <changbin.du@intel.com>
Cc: yamada.masahiro@socionext.com, michal.lkml@markovi.net,
tglx@linutronix.de, mingo@redhat.com, akpm@linux-foundation.org,
x86@kernel.org, lgirdwood@gmail.com, broonie@kernel.org,
arnd@arndb.de, linux-kbuild@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-arch@vger.kernel.org
Subject: Re: [PATCH 0/5] kernel hacking: GCC optimization for debug experience (-Og)
Date: Wed, 2 May 2018 13:09:18 +0200 [thread overview]
Message-ID: <20180502110917.wnat6cjxfbtrdh7t@gmail.com> (raw)
In-Reply-To: <20180502090756.tztulppgfefccd7q@intel.com>
* Du, Changbin <changbin.du@intel.com> wrote:
> On Wed, May 02, 2018 at 09:33:15AM +0200, Ingo Molnar wrote:
> >
> > * changbin.du@intel.com <changbin.du@intel.com> wrote:
> >
> > > Comparison of system performance: a bit drop.
> > >
> > > w/o CONFIG_DEBUG_EXPERIENCE
> > > $ time make -j4
> > > real 6m43.619s
> > > user 19m5.160s
> > > sys 2m20.287s
> > >
> > > w/ CONFIG_DEBUG_EXPERIENCE
> > > $ time make -j4
> > > real 6m55.054s
> > > user 19m11.129s
> > > sys 2m36.345s
> >
> > Sorry, that's not a proper kbuild performance measurement - there's no noise
> > estimation at all.
> >
> > Below is a description that should produce more reliable numbers.
> >
> > Thanks,
> >
> > Ingo
> >
> Thanks for your suggestion, I will try your tips to eliminate noise. Since it is
> tested in KVM guest, so I just reboot the guest before testing. But in host side
> I still need to consider these noises.
Please test the impact on the host, guest tests are typically too noisy for such
comparisons.
BTW., for guest tests rebooting the guest is not enough to replicate the method I
suggested.
Thanks,
Ingo
prev parent reply other threads:[~2018-05-02 11:09 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-01 13:00 [PATCH 0/5] kernel hacking: GCC optimization for debug experience (-Og) changbin.du
2018-05-01 13:00 ` [PATCH 1/5] x86/mm: surround level4_kernel_pgt with #ifdef CONFIG_X86_5LEVEL...#endif changbin.du
2018-05-01 13:00 ` [PATCH 2/5] regulator: add dummy of_find_regulator_by_node changbin.du
2018-05-01 20:40 ` Mark Brown
2018-05-02 9:24 ` Du, Changbin
2018-05-05 1:44 ` Applied "regulator: add dummy function of_find_regulator_by_node" to the regulator tree Mark Brown
2018-05-05 1:44 ` Mark Brown
2018-05-05 1:44 ` Mark Brown
2018-05-01 13:00 ` [PATCH 3/5] kernel hacking: new config NO_AUTO_INLINE to disable compiler atuo-inline optimizations changbin.du
2018-05-01 14:54 ` Steven Rostedt
2018-05-02 9:27 ` Du, Changbin
2018-05-01 13:00 ` [PATCH 4/5] kernel hacking: new config DEBUG_EXPERIENCE to apply GCC -Og optimization changbin.du
2018-05-01 15:25 ` Randy Dunlap
2018-05-02 9:24 ` Du, Changbin
2018-05-02 20:30 ` Arnd Bergmann
2018-05-01 13:00 ` [PATCH 5/5] asm-generic: fix build error in fix_to_virt with CONFIG_DEBUG_EXPERIENCE changbin.du
2018-05-02 7:33 ` [PATCH 0/5] kernel hacking: GCC optimization for debug experience (-Og) Ingo Molnar
2018-05-02 9:07 ` Du, Changbin
2018-05-02 11:09 ` Ingo Molnar [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=20180502110917.wnat6cjxfbtrdh7t@gmail.com \
--to=mingo@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=broonie@kernel.org \
--cc=changbin.du@intel.com \
--cc=lgirdwood@gmail.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.lkml@markovi.net \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
--cc=yamada.masahiro@socionext.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 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.