mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: yangyi <yang.yi@bmrtech.com>
To: LKML <linux-kernel@vger.kernel.org>
Cc: China Performance Team <china-perf@mvista.com>
Subject: 2.6 kernel series have noticeable performance regression
Date: Tue, 14 Jun 2005 15:14:24 +0800	[thread overview]
Message-ID: <1118733263.10339.1553.camel@montavista2> (raw)

Hi, All

I did a performance regression test for all the 2.6 kernel series on two
x86 platforms in last two weeks and found that some version kernels do
have noticeable performance regression, some performance indices have
about 20 to 30 percent regression,
 even several indices have over 30 percent fall.

For example, on Toshiba tecra8000 laptop: for 4-bytes packet, network
throughput of 2.6.11 is just about 57.5 percent of 2.6.0, for pipe
bandwidth, the value of 2.6.11 is just about 68 percent of that value of
2.6.0, for mmap latency, the value of 2.6.11 is about 1.8 times as long
as 2.6.0.

On supermicro-6012-p6, for 64-bytes small packet, network throughput of
2.6.11 is about 66.72 percent of 2.6.0, for 0K-size 2 processes context
switch time, 2.6.11 is 31.8 percent bigger than 2.6.0, for pipe latency,
2.6.10 is 35.85 percent bigger than 2.6.3.

So, I think that it is very very necessary to find the problems and fix
them ASAP.

The following articles give out all the test results, the article "2.6
kernel series have noticeable performance regression, part 1" gives out
the test results on SuperMicro-6012-p6, the article "2.6 kernel series
have noticeable performance regression, part 2" gives out the test
results on Toshiba tecra8000 laptop.



             reply	other threads:[~2005-06-14  7:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-14  7:14 yangyi [this message]
2005-06-14  8:46 ` Vincent Kergonna
2005-06-14  9:17   ` yangyi

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=1118733263.10339.1553.camel@montavista2 \
    --to=yang.yi@bmrtech.com \
    --cc=china-perf@mvista.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®