Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Refactor web host to use asynchronous I/O #28

Open
rcelyte opened this issue Feb 21, 2024 · 0 comments
Open

Refactor web host to use asynchronous I/O #28

rcelyte opened this issue Feb 21, 2024 · 0 comments
Labels
enhancement New feature or request server Involves BeatUpServer

Comments

@rcelyte
Copy link
Owner

rcelyte commented Feb 21, 2024

The current implementation spawns and detaches a new thread for every connection, making it extremely intensive and prone to resource exhaustion under load. It would be better to have a fixed pool of long running threads all simultaneously waiting on the listener socket, with each thread adding its share of incoming connections to a local connection list monitored via select/epoll/kqueue/IOCP.

@rcelyte rcelyte added enhancement New feature or request server Involves BeatUpServer labels Feb 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request server Involves BeatUpServer
Projects
None yet
Development

No branches or pull requests

1 participant