From: Rick Jones <rick.jones2@hp.com>
To: Feng Tang <feng.tang@intel.com>
Cc: David Miller <davem@davemloft.net>,
alex.shi@intel.com, eric.dumazet@gmail.com,
linux-kernel@vger.kernel.org, tim.c.chen@intel.com,
ying.huang@intel.com, netdev@vger.kernel.org
Subject: Re: TCP_STREAM performance regression on commit b3613118
Date: Tue, 06 Mar 2012 10:23:56 -0800 [thread overview]
Message-ID: <4F56563C.2070206@hp.com> (raw)
In-Reply-To: <20120306081117.GA17375@feng-i7>
On 03/06/2012 12:11 AM, Feng Tang wrote:
> On some machines, we found there is about 10% resgression of netperf
> TCP-64K loopback test between 3.2 and 3.3-rc1. The exact test is:
> ./netperf -t TCP_STREAM -l 60 -H 127.0.0.1 -i 50,3 -I 99,5 -- -s 32768 -S 32768 -m 4096
Side comment on the netperf command line. The maximum confidence
interactions is silently capped at 30, so that might as well be "-i
30,3"
http://www.netperf.org/svn/netperf2/tags/netperf-2.5.0/doc/netperf.html#index-g_t_002di_002c-Global-28
Also, for reproducibility, it might be desirable to pin netperf and
netserver to a specific CPU or CPUs. That would be with a global -T
option:
http://www.netperf.org/svn/netperf2/tags/netperf-2.5.0/doc/netperf.html#index-g_t_002dT_002c-Global-41
happy benchmarking,
rick jones
prev parent reply other threads:[~2012-03-06 18:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1329466694.12669.2976.camel@debian>
[not found] ` <1329472239.2861.3.camel@edumazet-HP-Compaq-6005-Pro-SFF-PC>
2012-02-17 18:33 ` TCP_STREAM performance regression on commit b3613118 David Miller
2012-02-20 1:44 ` Alex,Shi
2012-03-02 2:45 ` Alex Shi
2012-03-02 3:07 ` David Miller
2012-03-02 6:37 ` Alex Shi
2012-03-02 12:28 ` Eric Dumazet
2012-03-06 8:11 ` Feng Tang
2012-03-06 8:26 ` Jason Wang
2012-03-06 12:01 ` Eric Dumazet
2012-03-07 2:55 ` Feng Tang
2012-03-06 18:23 ` Rick Jones [this message]
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=4F56563C.2070206@hp.com \
--to=rick.jones2@hp.com \
--cc=alex.shi@intel.com \
--cc=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=feng.tang@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=tim.c.chen@intel.com \
--cc=ying.huang@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).