From: Felix Oxley <lkml@oxley.org>
To: Felix Oxley <lkml@oxley.org>
Cc: "Chen, Kenneth W" <kenneth.w.chen@intel.com>,
linux-kernel@vger.kernel.org
Subject: Re: kernel performance update - 2.6.14
Date: Sat, 29 Oct 2005 01:29:09 +0100 [thread overview]
Message-ID: <4362C255.30600@oxley.org> (raw)
In-Reply-To: <4362BFFC.9050202@oxley.org>
Felix Oxley wrote:
> Chen, Kenneth W wrote:
> > Kernel performance data for 2.6.14 (released yesterday) is updated at:
> > http://kernel-perf.sourceforge.net
> >
> > As expected, results are within run variation compares to 2.6.14-rc5.
> > No significant deviation found compare to 2.6.14-rc5
> >
>
> There seems to be some regression here:
>
> System: 4P Xeon
> Test:Result Group 8
> Metric: 64KB_4_fread
> Result: +1.9% -15%
> Kernel: 2.6.14-rc4 vs 2.6.14-rc4-git4
>
> System: 2P Xeon
> Test:Result Group 7
> Metric: ODIRECT
> Kernel: 2.6.14-rc5 vs 2.6.14-rc5-git3
> Summary: Write has increased whereas Read has decreased by 4-5 %
>
>
Something went horribly wrong with this test between 2.6.13 and
2.6.13-git2 (it has never recovered):
System: 4P Itanium
Test:Result Group 1
Metric: VolcanoMark
Result: -3% -10%
Kernel: 2.6.13 vs 2.6.13-git2
Does anybody know the cause of this?
regards,
Felix
next prev parent reply other threads:[~2005-10-29 0:29 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-28 23:44 kernel performance update - 2.6.14 Chen, Kenneth W
2005-10-28 23:54 ` Jeff Garzik
2005-10-28 22:43 ` Jeff V. Merkey
2005-10-29 2:49 ` Nick Piggin
2005-10-29 3:06 ` jmerkey
2005-10-29 3:08 ` jmerkey
2005-10-29 3:15 ` jmerkey
2005-10-29 8:38 ` Nick Piggin
2005-10-29 0:04 ` Chen, Kenneth W
2005-10-29 0:19 ` Felix Oxley
2005-10-29 0:29 ` Felix Oxley [this message]
2005-10-29 0:42 ` Chen, Kenneth W
2005-10-29 11:17 ` Dr. David Alan Gilbert
2005-10-29 0:29 ` Chen, Kenneth W
-- strict thread matches above, loose matches on Subject: below --
2005-11-08 0:04 Chen, Tim C
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=4362C255.30600@oxley.org \
--to=lkml@oxley.org \
--cc=kenneth.w.chen@intel.com \
--cc=linux-kernel@vger.kernel.org \
/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.