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

Feature: One event loop per core #7

Open
peters opened this issue Sep 3, 2014 · 1 comment
Open

Feature: One event loop per core #7

peters opened this issue Sep 3, 2014 · 1 comment

Comments

@peters
Copy link
Contributor

peters commented Sep 3, 2014

Maintain a master event loop that handles inbound connections. Then dispatch the connection to a slave loop which does the actual work. I think you might be able to achieve much better concurrency this way instead of using libuv's threadpool implementation.

@heapwolf
Copy link
Owner

heapwolf commented Sep 8, 2014

I think what you want is the ability to cluster?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants