From: Peter Zijlstra <peterz@infradead.org>
To: Vernon Mauery <vernux@us.ibm.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@redhat.com>, Jeff Garzik <jeff@garzik.org>
Subject: Re: [-RT] multiple streams have degraded performance
Date: Tue, 19 Jun 2007 08:51:38 +0200 [thread overview]
Message-ID: <1182235898.7348.361.camel@twins> (raw)
In-Reply-To: <200706182212.22633.vernux@us.ibm.com>
On Mon, 2007-06-18 at 22:12 -0700, Vernon Mauery wrote:
> In looking at the performance characteristics of my network I found that
> 2.6.21.5-rt15 suffers from degraded thoughput with multiple threads. The
> test that I did this with is simply invoking 1, 2, 4, and 8 instances of
> netperf at a time and measuring the total throughput. I have two 4-way
> machines connected with 10GbE cards. I tested several kernels (some older
> and some newer) and found that the only thing in common was that with -RT
> kernels the performance went down with concurrent streams.
>
> While the test was showing the numbers for receiving as well as sending, the
> receiving numbers are not reliable because that machine was running a -RT
> kernel for these tests.
>
> I was just wondering if anyone had seen this problem before or would have any
> idea on where to start hunting for the solution.
could you enable CONFIG_LOCK_STAT
echo 0 > /proc/lock_stat
<run your test>
and report the output of (preferably not 80 column wrapped):
grep : /proc/lock_stat | head
or otherwise if there are any highly contended network locks listed?
- Peter
next prev parent reply other threads:[~2007-06-19 6:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-19 5:12 [-RT] multiple streams have degraded performance Vernon Mauery
2007-06-19 6:51 ` Peter Zijlstra [this message]
2007-06-19 14:25 ` Vernon Mauery
2007-06-19 15:38 ` Peter Zijlstra
2007-06-19 17:19 ` Vernon Mauery
2007-06-20 3:38 ` Vernon Mauery
2007-06-20 7:42 ` Peter Zijlstra
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=1182235898.7348.361.camel@twins \
--to=peterz@infradead.org \
--cc=jeff@garzik.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=vernux@us.ibm.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.