From: Andrey Borzenkov <arvidjaar@mail.ru>
To: linux-kernel@vger.kernel.org
Subject: Number of open files scalability?
Date: Sat, 20 Jun 2009 13:32:47 +0400 [thread overview]
Message-ID: <200906201332.51953.arvidjaar@mail.ru> (raw)
[-- Attachment #1: Type: Text/Plain, Size: 975 bytes --]
Hi,
we have a customer that requires large number of open files. Basically,
it is SAP with large Oracle database with relatively large number of
concurrent connections from worker processes. Right now the amount
permanently opened files is above 128000; with current trends of DB and
load growth it could easily rocket up to and above of 1000000.
So the questions are
- is there any per-process or per-user limit for number of open files
imposed by kernel (except of course set by rlimits)?
- is there any fs/file-max limit except imposed by data type (int)?
- finally, how scalable is the implementation? Will having one million
of open files impose any noticeable slowdown? If yes, what operations
are affected? I.e. opening new files/creating new process is not that
important; but having to search 1000000 files for every operation would
be fatal.
The platform is x86_64, SLES 9 with likely update to SLES10.
Thank you!
-andrey
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
reply other threads:[~2009-06-20 9:38 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=200906201332.51953.arvidjaar@mail.ru \
--to=arvidjaar@mail.ru \
--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