From: "K.R. Foley" <kr@cybsft.com>
To: "Chen, Tim C" <tim.c.chen@intel.com>
Cc: mingo@elte.hu, linux-kernel@vger.kernel.org, "Siddha,
Suresh B" <suresh.b.siddha@intel.com>
Subject: Re: 2.6.19-rt14 slowdown compared to 2.6.19
Date: Fri, 22 Dec 2006 21:00:02 -0600 [thread overview]
Message-ID: <458C9BB2.1060201@cybsft.com> (raw)
In-Reply-To: <9D2C22909C6E774EBFB8B5583AE5291C0199950A@fmsmsx414.amr.corp.intel.com>
Chen, Tim C wrote:
> Ingo,
>
> We did some benchmarking on 2.6.19-rt14, compared it with 2.6.19
> kernel and noticed several slowdowns. The test machine is a 2 socket
> woodcrest machine with your default configuration.
>
> Netperf TCP Streaming was slower by 40% ( 1 server and 1 client
> each bound to separate cpu cores on different socket, network
> loopback mode was used).
>
> Volanomark was slower by 80% (Server and Clients communicate with
> network loopback mode. Idle time goes from 1% to 60%)
>
> Re-Aim7 was slower by 40% (idle time goes from 0% to 20%)
>
> Wonder if you have any suggestions on what could cause the slowdown.
> We've tried disabling CONFIG_NO_HZ and it didn't help much.
>
> Thanks.
>
> Tim
Take a look at this. Not sure if this is the same problem but it looks
like a candidate. I can definitely say that some latencies I have seen
in my recent testing have gone away in the last few versions
2.6.20-rc1-rt{3,4}.
Sorry I missed the URL first time around.
http://marc.theaimsgroup.com/?l=linux-kernel&m=116670388527349&w=2
--
kr
next prev parent reply other threads:[~2006-12-23 3:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-22 21:39 2.6.19-rt14 slowdown compared to 2.6.19 Chen, Tim C
2006-12-23 0:38 ` Daniel Walker
2006-12-23 2:43 ` K.R. Foley
2006-12-23 3:00 ` K.R. Foley [this message]
2006-12-23 10:59 ` Ingo Molnar
2006-12-29 23:52 ` Chen, Tim C
2006-12-30 10:04 ` Ingo Molnar
2007-01-02 18:07 ` Chen, Tim C
-- strict thread matches above, loose matches on Subject: below --
2006-12-27 0:51 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=458C9BB2.1060201@cybsft.com \
--to=kr@cybsft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=suresh.b.siddha@intel.com \
--cc=tim.c.chen@intel.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.