From: David Schwartz <davids@webmaster.com>
To: <mkingsbury@avayactc.com>,
"'linux-kernel@vger.kernel.org'" <linux-kernel@vger.kernel.org>
Subject: Re: High Rate of Sockets -> No buffer space availible errors
Date: Sat, 13 Oct 2001 10:13:02 -0700 [thread overview]
Message-ID: <20011013171303.AAA7749@shell.webmaster.com@whenever> (raw)
In-Reply-To: <CCE8403B91E4D4119E9300A0C9DDA22401C16AFD@pigpen.lucentctc.com>
On Sat, 13 Oct 2001 11:08:48 -0400, Kingsbury, Michael wrote:
>I have a network testing application that is opening & closing sockets with
>other machines at a high rate (multi-threaded, 1000 opens & closes a second
>with ~20 machines.) There's a seperate thread per machine its connecting
>to, and each thread opens a socket, transmits 8k, and closes.
Are these TCP sockets? It can take around 2 minutes to close a TCP
connection. So 1,000 opens/closes a second could potentially mean 120,000
connections sitting around. Are you sure you aren't running out of local
ports or something else?
>The problem lies with an error of 'No buffer space availible' within the
>first couple of seconds. I've tried the SO_SNDBUF& SO_RVCBUF, but that
>doesn't make sense in my head anyways. Anyone seen problems like this under
>similar conditions & maybe any remedys?
Which system call returns the error? socket? bind? send? receive?
And why are you using so many threads? Are you under the misperception that
you need lots of thread to do lots of work? Perhaps your architecture is a
major part of the problem.
DS
next prev parent reply other threads:[~2001-10-13 17:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-13 15:08 High Rate of Sockets -> No buffer space availible errors Kingsbury, Michael
2001-10-13 17:13 ` David Schwartz [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-10-13 20:58 Kingsbury, Michael
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=20011013171303.AAA7749@shell.webmaster.com@whenever \
--to=davids@webmaster.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mkingsbury@avayactc.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