public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "David Schwartz" <davids@webmaster.com>
To: "Chuck Winters" <cwinters@atl.lmco.com>, <linux-kernel@vger.kernel.org>
Subject: RE: Number of File descriptors
Date: Fri, 13 Jul 2001 23:03:07 -0700	[thread overview]
Message-ID: <NOEJJDACGOHCKNCOGFOMMEMGCHAA.davids@webmaster.com> (raw)
In-Reply-To: <20010713095934.A6100@atl.lmco.com>


> Hello All,
> 	My interest has been peaked by a recent email.  At one
> point, I heard two people speaking
> about how some database guy wanted to have 2000 open files(or
> something crazy like that).
> They said that he must be crazy because the kernel does a
> sequential search through the open
> file descriptors.  Anyway, I read a posting an a mail list that
> someone wanted select to
> select on 3000 files.  Alright, the question(Finally!):
> 		To have select() select on 3000 file descriptors,
> they must be open.  That's 3000 open
> 		files.  Will select be ultra slow trying to select
> on 3000 file descriptors?  Also,
> 		what is the clarification on the kernel doing a
> sequential search through the open
> 		file descriptors?

	Using 'select' on 3,000 file descriptors is not a problem. I have used
'poll' on 12,000 file descriptors with no problems at all. Performance is
not exactly stellar (you can use threads to improve it) but it's quite good.

	DS


  reply	other threads:[~2001-07-14  6:03 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-13 13:59 Number of File descriptors Chuck Winters
2001-07-14  6:03 ` David Schwartz [this message]
2001-07-17 13:46 ` Chuck Winters
2001-07-18 13:12   ` Patrick O'Rourke
  -- strict thread matches above, loose matches on Subject: below --
2001-07-14 15:06 Dan Kegel

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=NOEJJDACGOHCKNCOGFOMMEMGCHAA.davids@webmaster.com \
    --to=davids@webmaster.com \
    --cc=cwinters@atl.lmco.com \
    --cc=linux-kernel@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