From: Shaohua Li <shaohua.li@intel.com>
To: "Ted Ts'o" <tytso@mit.edu>
Cc: "Shi, Alex" <alex.shi@intel.com>,
"czoccolo@gmail.com" <czoccolo@gmail.com>,
"vgoyal@redhat.com" <vgoyal@redhat.com>,
"jaxboe@fusionio.com" <jaxboe@fusionio.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Chen, Tim C" <tim.c.chen@intel.com>
Subject: Re: [performance bug] kernel building regression on 64 LCPUs machine
Date: Thu, 20 Jan 2011 10:12:04 +0800 [thread overview]
Message-ID: <1295489524.1949.884.camel@sli10-conroe> (raw)
In-Reply-To: <20110119143214.GA3043@thunk.org>
On Wed, 2011-01-19 at 22:32 +0800, Ted Ts'o wrote:
> On Wed, Jan 19, 2011 at 09:55:48AM +0800, Alex,Shi wrote:
> > Shaohua and I tested kernel building performance on latest kernel. and
> > found it is drop about 15% on our 64 LCPUs NHM-EX machine on ext4 file
> > system.
>
> What kerenl version were you comparing against? And what were you
> using to benchmark this performance drop? I'm curious what your
> workload was; I'm guesisng it was some kind of mixed read/write
> workload? Were there any fsync()'s involved?
2.6.36 vs 2.6.37. this exists in 2.6.37-rc1. it's a kbuild, no a mixed
read/write workload. kbuild hasn't fsync involved
Thanks,
Shaohua
next prev parent reply other threads:[~2011-01-20 2:12 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-19 1:55 [performance bug] kernel building regression on 64 LCPUs machine Alex,Shi
2011-01-19 2:03 ` Shaohua Li
2011-01-19 12:56 ` Jan Kara
2011-01-20 7:52 ` Alex,Shi
2011-01-20 15:16 ` Vivek Goyal
2011-01-21 7:17 ` Shaohua Li
2011-01-26 8:15 ` Shaohua Li
2011-02-12 9:21 ` Alex,Shi
2011-02-12 18:25 ` Corrado Zoccolo
2011-02-14 2:25 ` Alex,Shi
2011-02-15 1:10 ` Shaohua Li
2011-02-21 16:49 ` Jan Kara
2011-02-23 8:24 ` Alex,Shi
2011-02-24 12:13 ` Jan Kara
2011-02-25 0:44 ` Alex Shi
2011-02-26 14:45 ` Corrado Zoccolo
2011-03-01 19:56 ` Jeff Moyer
2011-03-02 9:42 ` Jan Kara
2011-03-02 16:13 ` Jeff Moyer
2011-03-02 21:17 ` Jan Kara
2011-03-02 21:20 ` Jeff Moyer
2011-03-03 1:14 ` Jeff Moyer
2011-03-04 15:32 ` Jan Kara
2011-03-04 15:40 ` Jeff Moyer
2011-03-04 15:50 ` Jeff Moyer
2011-03-04 18:27 ` Jeff Moyer
2011-03-22 7:38 ` Alex,Shi
2011-03-22 16:14 ` Jan Kara
2011-03-22 17:46 ` Jeff Moyer
2011-03-24 6:45 ` Alex,Shi
2011-03-28 19:48 ` Jan Kara
2011-01-19 14:32 ` Ted Ts'o
2011-01-20 2:12 ` Shaohua Li [this message]
2011-01-21 7:23 ` Corrado Zoccolo
2011-01-21 7:47 ` Alex,Shi
2011-01-21 7:52 ` Alex,Shi
2011-01-21 8:13 ` Corrado Zoccolo
2011-01-21 8:20 ` Shaohua Li
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=1295489524.1949.884.camel@sli10-conroe \
--to=shaohua.li@intel.com \
--cc=alex.shi@intel.com \
--cc=czoccolo@gmail.com \
--cc=jaxboe@fusionio.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tim.c.chen@intel.com \
--cc=tytso@mit.edu \
--cc=vgoyal@redhat.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.