fix: speed up fd closing on Linux #54
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
On some AWS/container Linux environments
RLIMIT_NOFILE(and thereforesysconf(_SC_OPEN_MAX)) can be set extremely high (e.g. 1,048,576). Exile’s spawner was closing non-stdio fds by looping from 3.._SC_OPEN_MAX, which turns each spawn into ~1Mclose()syscalls and can add seconds of overhead even for trivial commands.Fix this on Linux by:
close_range(2)(Linux 5.9+) viasyscall()to efficiently close all fds >= 3 in the kernel./proc/self/fdand closing only the fds that are actually open (O(open_fds)).Non-Linux platforms keep the existing behavior unchanged.