raise file descriptor limit to 1024 by default #2884
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
License: MIT Signed-off-by: Jeromy <why@ipfs.io>
|
LGTM |
Closed
| @@ -9,7 +9,7 @@ import ( | |||
| "syscall" | |||
| ) | |||
|
|
|||
| var ipfsFileDescNum = uint64(2048) | |||
| var ipfsFileDescNum = uint64(1024) | |||
There was a problem hiding this comment.
is 1024 truly enough? why not 2048?
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This changes the behaviour of the ipfs daemon to raise the file descriptor ulimit to 1024 if it is below 1024 when the daemon starts.
On linux, this will have no effect.
On OSX, this will raise the file descriptor limit every time the daemon is started (as the default there is 256).
License: MIT
Signed-off-by: Jeromy why@ipfs.io