Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.lang.python > #15675 > unrolled thread

AW: Py2.7/FreeBSD: maximum number of open files

Started byTobias Oberstein <tobias.oberstein@tavendo.de>
First post2011-11-14 08:36 -0800
Last post2011-11-14 08:36 -0800
Articles 1 — 1 participant

Back to article view | Back to comp.lang.python

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.


Contents

  AW: Py2.7/FreeBSD: maximum number of open files Tobias Oberstein <tobias.oberstein@tavendo.de> - 2011-11-14 08:36 -0800

#15675 — AW: Py2.7/FreeBSD: maximum number of open files

FromTobias Oberstein <tobias.oberstein@tavendo.de>
Date2011-11-14 08:36 -0800
SubjectAW: Py2.7/FreeBSD: maximum number of open files
Message-ID<mailman.2700.1321289211.27778.python-list@python.org>
> I'm not familiar with BSD but Linux has similar Kernel options. The kernel
> options might be *global* flags to set the total upper limit of open file
> descriptors for the entire system, not for a single process.
> Also on Linux "ulimit" doesn't display the fd limit. You have to use "ulimit -n".

This is a dedicated machine doing nothing else .. I'm monitoring global FD usage

sysctl kern.openfiles

and it's way beyond the configured limit

$ ulimit -n
200000


> 
> Why do you need more than 32k file descriptors anyway? It's an insanely high

It's not for files:

This is a network service .. I tested it with up to 50k TCP connections .. however
at this point, when the service tries to open a file, it'll bail out.

Sockets+Files both contribute to open FDs.

I need 50k sockets + 100 files.

Thus, this is even more strange: the Python (a Twisted service) will happily
accept 50k sockets, but as soon as you do open() a file, it'll bail out.

[toc] | [standalone]


Back to top | Article view | comp.lang.python


csiph-web