From: Eli Zaretskii <eliz@gnu.org>
To: Robert Pluim <rpluim@gmail.com>
Cc: monnier@iro.umontreal.ca, emacs-devel@gnu.org
Subject: Re: Surprisingly high use of file descriptors
Date: Thu, 05 May 2022 10:47:26 +0300 [thread overview]
Message-ID: <83ee182zg1.fsf@gnu.org> (raw)
In-Reply-To: <87r1585u5k.fsf@gmail.com> (message from Robert Pluim on Thu, 05 May 2022 09:13:27 +0200)
> From: Robert Pluim <rpluim@gmail.com>
> Cc: emacs-devel@gnu.org
> Date: Thu, 05 May 2022 09:13:27 +0200
>
> Stefan> Why would ``lsp-mode` or `eglot` consume anywhere near 1024 file descriptors?
> Stefan> Are they launching a separate LSP server process per buffer?
>
> They use filenotify.el to watch for the changes to all the files in
> their project, which on some platforms consumes a file descriptor per
> file (at least macOS, and anything kqueue based like FreeBSD). On
> other platforms it uses one per directory, and Iʼm sure people have
> codebases with >1024 directories.
FTR, on MS-Windows the implementation uses a file handle per watch
(one watch for each directory), but that handle is not monitored by
the emulated pselect. It also creates one thread per each watch. The
maximum number of file handles per process on MS-Windows is AFAIK very
large (in the millions), and the maximum number of threads per process
is on the order of tens of thousands.
next prev parent reply other threads:[~2022-05-05 7:47 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-04 15:22 1024 file descriptors should be enough for anyone Robert Pluim
2022-05-05 0:55 ` Po Lu
2022-05-05 2:51 ` Po Lu
2022-05-05 7:09 ` Robert Pluim
2022-05-06 8:28 ` Robert Pluim
2022-05-06 8:54 ` Po Lu
2022-05-06 9:02 ` Robert Pluim
2022-05-06 9:28 ` Po Lu
2022-05-06 9:31 ` Robert Pluim
2022-05-06 10:41 ` Po Lu
2022-05-06 12:21 ` Robert Pluim
2022-05-06 13:04 ` Po Lu
2022-05-06 13:20 ` Po Lu
2022-05-06 16:41 ` Robert Pluim
2022-05-05 2:11 ` Surprisingly high use of file descriptors Stefan Monnier
2022-05-05 7:13 ` Robert Pluim
2022-05-05 7:47 ` Eli Zaretskii [this message]
2022-05-05 7:51 ` Robert Pluim
2022-05-05 8:20 ` Eli Zaretskii
2022-05-05 8:25 ` Robert Pluim
2022-05-05 11:35 ` 1024 file descriptors should be enough for anyone Lars Ingebrigtsen
2022-05-05 12:30 ` Robert Pluim
2022-05-05 13:12 ` Lars Ingebrigtsen
2022-05-05 13:45 ` Robert Pluim
2022-05-24 23:50 ` Lars Ingebrigtsen
2022-05-25 15:30 ` Robert Pluim
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83ee182zg1.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=rpluim@gmail.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).