netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: rapier <rapier@psc.edu>
To: netdev@vger.kernel.org
Subject: [Question] TCP stack performance decrease since 3.14
Date: Wed, 15 Apr 2015 15:31:52 -0400	[thread overview]
Message-ID: <552EBCA8.6090408@psc.edu> (raw)

All,

First, my apologies if this came up previously but I couldn't find 
anything using a keyword search of the mailing list archive.

As part of the on going work with web10g I need to come up with baseline 
TCP stack performance for various kernel revision. Using netperf and 
super_netperf* I've found that performance for TCP_CC, TCP_RR, and 
TCP_CRR has decreased since 3.14.

	3.14	3.18	4.0 	decrease %
TCP_CC	183945	179222	175793	4.4%
TCP_RR	594495	585484	561365	5.6%
TCP_CRR	98677	96726	93026	5.7%

Stream tests have remained the same from 3.14 through 4.0.

All tests were conducted on the same platform from clean boot with stock 
kernels.

So my questions are:

Has anyone else seen this or is this a result of some weirdness on my 
system or artifact of my tests?

If others have seen this or is just simply to be expected (from new 
features and the like) is it due to the TCP stack itself or other 
changes in the kernel?

If so, is there anyway to mitigate the effect of this via stack tuning, 
kernel configuration, etc?

Thanks!

Chris


* The above results are the average of 10 iterations of super_netperf 
for each test. I can run more iterations to verify the results but it 
seem consistent. The number of parallel processes for each test was 
tuned to produce the maximum test result. In other words, enough to push 
things but not enough to cause performance hits due to being 
cpu/memory/etc bound. If anyone wants the full results and test scripts 
just let me know.

             reply	other threads:[~2015-04-15 20:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-15 19:31 rapier [this message]
2015-04-15 21:01 ` [Question] TCP stack performance decrease since 3.14 Eric Dumazet
2015-04-15 21:38   ` rapier
2015-04-15 22:13     ` Eric Dumazet
2015-04-15 21:31 ` Rick Jones

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=552EBCA8.6090408@psc.edu \
    --to=rapier@psc.edu \
    --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 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).