netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Priebe - Profihost AG <s.priebe@profihost.ag>
To: netdev@vger.kernel.org
Subject: slow TCP speed through linux ip forwarding
Date: Tue, 16 Jun 2015 12:35:06 +0200	[thread overview]
Message-ID: <557FFBDA.9040501@profihost.ag> (raw)

Hello,

i hope somebody has an idea for my problem and may point me to the right
direction. Alle servers run kernel 3.18.14.

My problem is that i can't archieve more than 20Mbit/s using a single
TCP stream and i've no further ideas how to solve it.

reduced Network Map

Server A
  |
Linux GW Server
  |
Brocade Router  - Server B
  |
Internet
  |
Server C

The Linux GW Server does nothing more than being an ip forwarding GW.
(no iptables / packet filtering).

I've done the following Tests while the Linux GW has a traffic of around
500-600Mbit/s:

Download file from Server A to C: 10-20Mbit/s
Download file from Server A to B: 100Mbit/s
Download file from Server B to C: 100Mbit/s

4 parallel downloads from Server A to C: 80-100Mbit/s

Same test with no other traffic on the Linux GW:

Download file from Server A to C: 100Mbit/s
Download file from Server A to B: 100Mbit/s
Download file from Server B to C: 100Mbit/s

4 parallel downloads from Server A to C: 100Mbit/s

Same test with net.ipv4.tcp_congestion_control=bic on Server A:

Download file from Server A to C: 70Mbit/s
Download file from Server A to B: 100Mbit/s
Download file from Server B to C: 100Mbit/s

4 parallel downloads from Server A to C: 80-100Mbit/s

ehtootl -S shows no errors for eth0 and eth1 on the linux gw.

I've no further ideas.

Thanks a lot.

Greets,
Stefan

                 reply	other threads:[~2015-06-16 10:35 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=557FFBDA.9040501@profihost.ag \
    --to=s.priebe@profihost.ag \
    --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).