netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: bert hubert <ahu@ds9a.nl>
To: Christian Schmid <webmaster@rapidforum.com>
Cc: Nivedita Singhvi <niv@us.ibm.com>, netdev@oss.sgi.com
Subject: many outgoing tcp sockets are slower than a few
Date: Mon, 21 Feb 2005 10:01:21 +0100	[thread overview]
Message-ID: <20050221090121.GA7478@outpost.ds9a.nl> (raw)
In-Reply-To: <42192CD5.5090401@rapidforum.com>

On Mon, Feb 21, 2005 at 01:35:33AM +0100, Christian Schmid wrote:

> New connections get made without any problems. Just existing connections 
> slow down painfully.

Incoming our outgoing data mostly?

> 3000 sockets = no slowdown at all (500 MBit in use)
> 3300 sockets = 10% slowdown
> 3600 sockets = 30% slowdown
> 4000 sockets = 60% slowdown (i aborted here, as it only uses 200 MBit for 
> sending... catastrophy!)
> 
> They are all receiving data. Its a download-service. receive-buffer is set 
> to 24 KB and send-buffer set to 224 KB. I don't see a problem with 
> port-space. I only have 3500 sockets when the problem appears but it 
> appears suddenly.

I'm a bit confused, it is a download service so you are probably *sending*
data? 

> >But it would help if you looked at the stats and ifconfig
> >to see who's dropping packets, how many retransmissions there
> >are, memory failures, or the bottleneck is some other issue altogether...
> 
> No way. Doing 30000 packets per second and your stats are 32 bit integers ;)

So? You could be a bit more helpful. Sample over 5 seconds, you won't
overflow that.

Also, can you tcpdump a bit? Are you using iptables? The conntrack table
might be slowing you down. 

I have a hunch this problem has to do with high-mem issues though.

Good luck!

-- 
http://www.PowerDNS.com      Open source, database driven DNS Software 
http://netherlabs.nl              Open and Closed source services

  reply	other threads:[~2005-02-21  9:01 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-21  0:05 Annoying bug with many sockets Christian Schmid
2005-02-21  0:26 ` Nivedita Singhvi
2005-02-21  0:35   ` Christian Schmid
2005-02-21  9:01     ` bert hubert [this message]
2005-02-21 10:36       ` many outgoing tcp sockets are slower than a few Christian Schmid
2005-02-21 12:02         ` Lennert Buytenhek
2005-02-21 12:25           ` bert hubert
2005-02-21 12:36             ` Lennert Buytenhek
2005-02-21 17:17           ` Christian Schmid
2005-02-21 17:24             ` bert hubert
2005-02-21 19:10               ` Christian Schmid
2005-02-21 17:29             ` Lennert Buytenhek
2005-02-21 19:11               ` Christian Schmid
2005-02-21 13:59         ` Baruch Even

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=20050221090121.GA7478@outpost.ds9a.nl \
    --to=ahu@ds9a.nl \
    --cc=netdev@oss.sgi.com \
    --cc=niv@us.ibm.com \
    --cc=webmaster@rapidforum.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).