feat(server): remove ulimit #1447
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
This is unnecessarily restricting the server, which limits the number of connections we can support. It also can't raise the ulimit, since the host impose a cap on the container. Service providers can still set the ulimit on their host if they want to.
|
Any thoughts? |
daniellacosse
approved these changes
Nov 15, 2023
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 is unnecessarily restricting the server, which limits the number of connections we can support. This affected one of our partners. The call also can't raise the ulimit, since the host impose a cap on the container.
Those measurements were done when we uses ss-server, which we haven't used for several years.
Service providers can still set the ulimit on their host if they want to.