From: Vernon Mauery <vernux@us.ibm.com>
To: Vernon Mauery <vernux@us.ibm.com>, LKML <linux-kernel@vger.kernel.org>
Cc: Ingo Molnar <mingo@redhat.com>, Jeff Garzik <jeff@garzik.org>
Subject: [-RT] multiple streams have degraded performance
Date: Mon, 18 Jun 2007 22:12:21 -0700 [thread overview]
Message-ID: <200706182212.22633.vernux@us.ibm.com> (raw)
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.
--Vernon
The key for this is 'default' was invoked like:
netperf -c -C -l 60 -H 10.2.2.4 -t UDP_STREAM -- -m 1472 -M 1472
and '1Msock' was invoked like:
netperf -c -C -l 60 -H 10.2.2.4 -t UDP_STREAM -- -m 1472 -M 1472 -s 1M -S 1M
2.6.21
==============
default: 1 streams: Send at 2844.2 Mb/s, Receive at 2840.1 Mb/s
default: 2 streams: Send at 3927.9 Mb/s, Receive at 3603.9 Mb/s
default: 4 streams: Send at 4197.4 Mb/s, Receive at 3776.3 Mb/s
default: 8 streams: Send at 4223.9 Mb/s, Receive at 3848.9 Mb/s
1Msock: 1 streams: Send at 4232.3 Mb/s, Receive at 3914.4 Mb/s
1Msock: 2 streams: Send at 5428.8 Mb/s, Receive at 3853.2 Mb/s
1Msock: 4 streams: Send at 6202.1 Mb/s, Receive at 3774.8 Mb/s
1Msock: 8 streams: Send at 6225.1 Mb/s, Receive at 3754.7 Mb/s
2.6.21.5-rt15
===============
default: 1 streams: Send at 3091.6 Mb/s, Receive at 3048.1 Mb/s
default: 2 streams: Send at 3768.8 Mb/s, Receive at 3714.2 Mb/s
default: 4 streams: Send at 1873.6 Mb/s, Receive at 1825.9 Mb/s
default: 8 streams: Send at 1806.5 Mb/s, Receive at 1792.7 Mb/s
1Msock: 1 streams: Send at 3680.4 Mb/s, Receive at 3255.6 Mb/s
1Msock: 2 streams: Send at 4129.8 Mb/s, Receive at 3991.5 Mb/s
1Msock: 4 streams: Send at 1862.1 Mb/s, Receive at 1787.1 Mb/s
1Msock: 8 streams: Send at 1790.2 Mb/s, Receive at 1556.8 Mb/s
next reply other threads:[~2007-06-19 5:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-19 5:12 Vernon Mauery [this message]
2007-06-19 6:51 ` [-RT] multiple streams have degraded performance Peter Zijlstra
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=200706182212.22633.vernux@us.ibm.com \
--to=vernux@us.ibm.com \
--cc=jeff@garzik.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox