Feature/non blocking tcp #2
Merged
Conversation
This file contains hidden or 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
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 PR implements a non-blocking TCP acceptor to handle incoming requests more efficiently. Each request is now assigned to a dedicated web_server_tcp_acceptor process, supervised by web_server_tcp_listener_sup and invoked by web_server_tcp_listener. This change aims to enhance scalability and responsiveness by ensuring that the system can handle multiple concurrent connections without blocking.
Additional adjustments were made to address process termination issues, ensuring proper cleanup of resources after a request ends. Stress tests were conducted to validate the changes, with ongoing refinements to resolve any remaining edge cases (e.g., EOF errors).