From: Weiping Pan <wpan@redhat.com>
To: Eric Dumazet <erdnetdev@gmail.com>
Cc: davem@davemloft.net, brutus@google.com, netdev@vger.kernel.org
Subject: Re: [RFC PATCH net-next 4/4 V4] try to fix performance regression
Date: Thu, 13 Dec 2012 22:09:12 +0800 [thread overview]
Message-ID: <50C9E188.8080503@redhat.com> (raw)
In-Reply-To: <1355329523.9139.578.camel@edumazet-glaptop>
On 12/13/2012 12:25 AM, Eric Dumazet wrote:
> On Wed, 2012-12-12 at 22:29 +0800, Weiping Pan wrote:
>
>> MS BASE AF_UNIX FRIENDS TCP_STREAM_MS
>> 1 10.70 5.40 4.02 37% 74%
>> 2 28.01 9.67 7.97 28% 82%
>> 4 55.53 19.78 16.48 29% 83%
>> 8 115.40 38.22 33.51 29% 87%
>> 16 227.31 81.06 67.70 29% 83%
>> 32 446.20 166.59 129.31 28% 77%
>> 64 849.04 336.77 259.43 30% 77%
>> 128 1440.50 661.88 530.43 36% 80%
>> 256 2404.70 1279.67 1029.15 42% 80%
>> 512 4331.53 2501.30 1942.21 44% 77%
>> 1024 6819.78 4622.37 4128.10 60% 89%
>> 2048 10544.60 6348.81 6349.59 60% 100%
>> 4096 12830.41 8324.43 7984.43 62% 95%
>> 8192 13462.65 8355.49 11079.37 82% 132%
>> 16384 9960.87 10840.13 13037.81 130% 120%
>> 32768 8749.31 11372.15 15087.08 172% 132%
>> 65536 7580.27 12150.23 14971.42 197% 123%
>> 131072 6727.74 11451.34 13604.78 202% 118%
>> 262144 7673.14 11613.10 11436.97 149% 98%
>> 524288 7366.17 11675.95 11559.43 156% 99%
>> 1048576 6608.57 11883.01 10103.20 152% 85%
>> MS means Message Size in bytes, that is -m -M for netperf
> I cant reproduce your strange numbers here, they make no sense to me.
>
> for s in 1 2 4 8 16 32 64 128 256 512 1024 2048 4096 8192 16384 32768
> 65536 131072 262144 524288 1048576
> do
> ./netperf -- -m $s -M $s | tail -n1
> done
>
> Results :
>
> 87380 16384 1 10.00 34.68
> 87380 16384 2 10.00 68.07
> 87380 16384 4 10.00 126.27
> 87380 16384 8 10.00 284.50
> 87380 16384 16 10.00 574.38
> 87380 16384 32 10.00 1091.74
> 87380 16384 64 10.00 2130.23
> 87380 16384 128 10.00 4001.83
> 87380 16384 256 10.00 7666.01
> 87380 16384 512 10.00 13425.81
> 87380 16384 1024 10.00 21146.43
> 87380 16384 2048 10.00 28551.42
> 87380 16384 4096 10.00 37878.95
> 87380 16384 8192 10.00 42507.23
> 87380 16384 16384 10.00 46782.53
> 87380 16384 32768 10.00 42410.97
> 87380 16384 65536 10.00 43053.09
> 87380 16384 131072 10.00 44504.20
> 87380 16384 262144 10.00 50211.74
> 87380 16384 524288 10.00 54004.23
> 87380 16384 1048576 10.00 53852.26
>
>
>
Hi, Eric,
In my test program, I run normal tcp loopback then friends for each
message size,
then it generates such strange numbers.
But if I just run normal tcp loopback for each message size, then the
performance is stable.
Maybe I should make the environment clean before each test, like
dropping cache.
thanks
Weiping Pan
prev parent reply other threads:[~2012-12-13 14:09 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-18 10:19 Fwd: Re: [PATCH v3] net-tcp: TCP/IP stack bypass for loopback connections Weiping Pan
2012-10-18 12:23 ` Bruce Curtis
2012-12-05 2:54 ` [RFC PATCH net-next 0/3 V4] " Weiping Pan
2012-12-05 2:54 ` [PATCH 1/3] Bruce's orignal tcp friend V3 Weiping Pan
2012-12-05 2:54 ` [PATCH 2/3] fix panic in tcp_close() Weiping Pan
2012-12-05 2:54 ` [PATCH 3/3] delete request_sock->friend Weiping Pan
2012-12-10 21:02 ` [RFC PATCH net-next 0/3 V4] net-tcp: TCP/IP stack bypass for loopback connections David Miller
2012-12-12 14:13 ` Weiping Pan
[not found] ` <117a10f9575d95d6a9ea4602ea7376e2b6d5ccd1.1355320533.git.wpan@redhat.com>
2012-12-12 14:29 ` [RFC PATCH net-next 4/4 V4] try to fix performance regression Weiping Pan
2012-12-12 14:57 ` David Laight
2012-12-13 14:05 ` Weiping Pan
2012-12-13 18:25 ` Rick Jones
2012-12-14 5:53 ` Weiping Pan
2012-12-12 16:25 ` Eric Dumazet
2012-12-13 14:09 ` Weiping Pan [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=50C9E188.8080503@redhat.com \
--to=wpan@redhat.com \
--cc=brutus@google.com \
--cc=davem@davemloft.net \
--cc=erdnetdev@gmail.com \
--cc=netdev@vger.kernel.org \
/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.