From: Nivedita Singhvi <niv@us.ibm.com>
To: Christian Schmid <webmaster@rapidforum.com>
Cc: netdev@oss.sgi.com
Subject: Re: Annoying bug with many sockets.
Date: Sun, 20 Feb 2005 16:26:23 -0800 [thread overview]
Message-ID: <42192AAF.8020609@us.ibm.com> (raw)
In-Reply-To: <421925DB.2060602@rapidforum.com>
Christian Schmid wrote:
> Hi.
>
> This is really annoying. With 3500 sockets onwards, linux 2.6.10
> completely lags. This is a bug and I am not willing to buy new servers
> just because linux has a BUG. tcp_mem _rmem and _wmem have been set to
> 1024000 for testing but this doesnt help as well. so whats WRONG
> there... please?
>
> Best regards,
> Chris
You have not actually said what the problem is - do
new connections not get made? Or existing connections
slow down?
You are trying to run many simultaneous connections, so
bumping up the individual socket buffer allocation will
not necessarily help - you need to bump up the global
TCP limit (tcp_mem[]) - it's a 3-tuple - if you have
the memory in your system, bump it way up. netstat -tan
will tell you if there is unread data in the queues..
Are you running into memory pressure? Or aborts?
netstat -s might give you some info on what is happening.
Bump up the port space (/proc/sys/net/ipv4/ip_local_port_range)
available - typical default is 32K - 61000 (can lower min to 4K)
Are they all receiving data or sending? Are they talking to
different hosts?
You can increase tcp_max_syn_backlog, core/netdev_max_backlog,
for a start.
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...
thanks,
Nivedita
next prev parent reply other threads:[~2005-02-21 0:26 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 [this message]
2005-02-21 0:35 ` Christian Schmid
2005-02-21 9:01 ` many outgoing tcp sockets are slower than a few bert hubert
2005-02-21 10:36 ` 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=42192AAF.8020609@us.ibm.com \
--to=niv@us.ibm.com \
--cc=netdev@oss.sgi.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).