[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4F56563C.2070206@hp.com>
Date: Tue, 06 Mar 2012 10:23:56 -0800
From: Rick Jones <rick.jones2@...com>
To: Feng Tang <feng.tang@...el.com>
CC: David Miller <davem@...emloft.net>, alex.shi@...el.com,
eric.dumazet@...il.com, linux-kernel@...r.kernel.org,
tim.c.chen@...el.com, ying.huang@...el.com, netdev@...r.kernel.org
Subject: Re: TCP_STREAM performance regression on commit b3613118
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
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists